Scheduling and publishing posts

Setting the time

Finish a post in the composer and you give it a date and time. That writes a scheduled entry onto the calendar, carrying the creative, the target channel, and the payload built for each platform. Changed your mind? Drag the post to a new day on the grid, or open it and pick a new time. Scheduling is limited to members who can edit organization content.

How a post goes out

A post does not publish the second you schedule it. A background job runs on its own interval, wakes up, finds entries whose time has come, and sends them to their channels. The calendar is the plan; that job is the courier that carries it out. Think of it like a letter with a future postmark: writing the date on the envelope is a promise, not the delivery.

Reading the real result

This is the least proven part of the surface, so trust the status, not your intentions. A post can come back as published, as failed, or as a non-live state the platform calls simulated or processing, which means it was accepted but is not publicly live yet, usually because an access review or sandbox tier is still pending. Open any post to see its status, how many attempts it has made, the last error, and a Retry button. In production so far, only one scheduled post has published while three have failed, so this path is rough rather than routine. After a scheduled time passes, open the post and confirm it rather than assuming it went out.