Configure queues and publication time slots

Understand a queue and its slots

A queue is a publication lane: it groups channels, timing rules and approval-flow defaults. A slot is one recurring rule in that lane. A time slot is a specific occurrence of the rule, such as the next Monday at a chosen UTC time. A post needs that concrete occurrence to enter the planned publication flow.

Queues organize when eligible posts can be dispatched. They do not automatically write content or make every item publish repeatedly. Use Post schedulers when you need future posts generated from a published source. Begin with one queue and one understandable timing rule so you can inspect the full result.

Create a queue and attach destinations

1. Open Queues and use Create Queue. Enter a recognizable name for the publication lane.
2. Select the relevant channels during creation or attach them from the queue details.
3. Add an initial slot or open the slots area to configure one after saving.
4. Check that the queue is active and that its channels and required connections are usable.

A queue can be created before its destination setup is complete, but that does not make it publishable. When scheduling a post, its selected channels must be attached to the chosen queue and pass current availability checks. If the queue does not appear for a post, compare its channel membership with the post's targets before creating another queue.

Configure slot rules

A slot has a name, a cron expression, a start time, an optional expiry and an enabled state. The current scheduler uses standard five-field UTC cron expressions. For example, 0 9 * * 1-5 describes 09:00 UTC on weekdays. Confirm the generated occurrences in the calendar or range view before assigning a campaign.

Queue-local time zones and second-level cron fields are outside this version's scheduling model. A local clock can move with daylight-saving changes while a UTC rule stays fixed. Set the start and expiry deliberately, and disable an unused slot. A valid rule with no occurrence in the selected date range is different from a broken scheduler.

Set review defaults and check capacity

Add the required Lifecycle approval-flow reference to the queue and choose its default where appropriate. Posts resolve that default as part of submission or scheduling. Queue settings do not replace the review workflow; they help apply the intended workflow consistently to the lane.

Several posts can share an occurrence if capacity permits. The current implementation's default is five active post bindings at the same execution time across queues in the workspace. Use the availability display and its remaining-capacity result as the authority for your deployment. Drafts and active publication states are treated differently; activating or submitting a draft can require another capacity check. Moving to another queue at the same time may therefore leave the same conflict.

Change a queue without losing track of planned work

Changing a slot rule, disabling it, removing a channel or making a queue inactive can block posts that relied on that configuration. Review affected future posts and reschedule them against valid occurrences. Historical publication results remain separate from the new schedule. Do not assume that moving the rule automatically moves every approved post to a replacement time.

Due occurrences are processed within a 30-minute dispatch window. Execution history records outcomes, including occasions where no eligible post was found. Inspect the linked post and its channel receipts when a queue has not recorded a successful publication. For persistent problems, check active state, occurrence time, channel membership, review completion and capacity in that order, then follow publishing troubleshooting.