Schedule a post and generate recurring content

Choose the right scheduling approach

Use a one-time schedule for a particular announcement. Use a queue occurrence when a post belongs in an established publication lane. Use a Post scheduler when you want future posts generated from a suitable published source. These are related tools, but configuring a recurring queue rule alone does not create new content.

Before scheduling, confirm active destination channels, valid content and any required approval flow. For queue publishing, the selected destinations must belong to the queue. Read Queues and time slots if you need to create the lane or adjust its publication rules first.

Schedule one post

1. Open the post's scheduling controls and choose One time or Queue time slot.
2. For one-time publication, select a valid future date and time. For a queue, choose the queue and a concrete available occurrence in the displayed range.
3. Check the displayed time zone and final scheduled time. Queue cron rules and occurrence calculations use UTC.
4. Confirm the schedule and complete any required approval. Reopen the Planner or post details to verify the saved occurrence.

Availability is checked again when the selection is saved. If another post takes the remaining capacity, refresh and choose another time. Scheduling is a request for eligible dispatch, not a guarantee that a provider will publish at an exact second.

Create a Post scheduler

A scheduler starts from an eligible Published post that used Queue-slot scheduling. The source supplies its queue, and you select one or more enabled slots in that queue. You can choose other enabled slots; the source's original slot is not mandatory. If the source list is empty, confirm the source post's published state, schedule mode, queue and your access.

Choose Shared or Private visibility. Shared schedulers are visible to authorized workspace users; Private schedulers are visible to their owner. Set the generation mode and lead time, then create the scheduler. Creation records the configuration; background processing produces the due future posts and their generation history.

Choose content and review behavior

Clone uses the source content. AI requires an available registered Posts Agent and nonempty instructions explaining how each generated post should change. Check the generated result, particularly claims, dates and channel variants. The presence of an AI option does not establish that the Agent worker or its provider is ready in your deployment.

Draft generation leaves the generated post as a draft. New generation enters the existing queue workflow; with AI, that happens only after generation succeeds. Set Generate before using days and hours. Zero generates at publication time; the supported nonzero lead time starts at one hour and is bounded to 365 days. Allow enough time for review and correction.

Maintain recurring work

Inspect the scheduler's generated-post history and AI status. A retryable generation problem is handled against the same generated post, avoiding a second copy for the same occurrence. Do not create replacement schedulers simply because a background run has not yet completed.

Deactivating a scheduler stops future generation; it does not cancel or delete posts already generated. Review those posts individually when stopping a campaign. Changing a slot can pause obsolete planned posts, and deleting a selected slot can cancel its scheduler. After queue changes, inspect both scheduler history and the Planner. For a paused, rejected or expired post, use the available correction and rescheduling flow instead of assuming it will catch up automatically.