Queue

Everything booked to publish, and everything that already did. Studio, then Queue.

Active shows pending, publishing, failed and expired, the ones only a human can still act on. History shows the last 20 published and skipped slots.

The header shows the next free slot in your schedule, so you know how far out you are booked.

Statuses

Status	Meaning
pending	Waiting for its time
publishing	In flight right now
published	Done, with a link to the live post
skipped	You cancelled it
failed	Something went wrong
expired	Its time arrived with the post still unapproved, so it never published

A pending slot still waiting a few minutes past its time turns amber and says not picked up. Nothing is wrong with the post itself, and it goes out as soon as it is picked up.

Actions

Reschedule moves a pending or expired slot to a new time. It refuses a time already booked for the same account, with "Another slot is already booked at that time." Rescheduling an expired slot on a post nobody has approved yet still needs that approval before the new time.

Skip cancels a pending, failed or expired slot. One way, and it does not touch the draft, so you can schedule it again later.

Retry puts a failed slot back to pending. It does not re-run immediately: the next scheduler tick picks it up, within a minute.

A published slot can also carry its own retry for a first comment, a repost or a thread follow-up that failed after the lead post itself went out fine: retry just that piece without touching the publish.

When a slot fails

The draft stays scheduled rather than reverting, so nothing is lost and you can inspect it.

Each publish gets 3 attempts with increasing backoff, so a transient network problem usually resolves itself. A slot that reaches failed has genuinely exhausted those.

Common causes:

Cause	Fix
Connection needs reauth	Reconnect under Settings, then Connections
Media missing or invalid	Add a slide to the carousel, or re-upload the video
Platform rejected the content	Read the error on the slot, edit the draft, reschedule
Platform outage	Retry

"Verify manually"

A slot asking you to verify manually has NOT been retried

Publishing is not idempotent: a platform has no way to tell us "you already posted this". So each slot journals its progress immediately before the irreversible go-live call.

If a retry finds a slot where the call was attempted, there was no clean failure, and no post id came back, it stops. It will not publish again.

Check the platform yourself. If the post is there, skip the slot and mark the draft posted. If it is not, retry.

Posting twice is worse than posting late, which is why it errs this way.

Nothing is publishing

Check in order:

1. The slot time, in your posting timezone rather than yours-in-your-head.
2. The connection status. An account in needs_reauth cannot publish.
3. Approval. A slot on a post nobody has approved yet expires instead of publishing. See Approve and schedule.
4. The platform. Threads and Facebook posting depends on Meta's own app review, separate from anything in Postlyra. See Platform support.