Scheduling and posting
Picking a time, moving a post you already scheduled, and why one is waiting for approval.
- How do I choose when a post goes out?
- How do I move a post I already scheduled?
- How close to the scheduled minute does it actually publish?
- Why is my post sitting in Approvals?
How do I choose when a post goes out?
The composer gives you three: Now, Queue (the next free slot in your posting schedule, shown on the button so it isn't a blind choice), and Pick a time.
The queue starts at 11:00 and 17:00 every day. Change the slots under Project settings → Queue, where you can also add a few minutes of random jitter so your posts don't land on the same minute forever.
How do I move a post I already scheduled?
Drag it on the calendar. In month view, dropping it on another day keeps its time of day; in week view you're dropping it on a specific hour. Hovering an empty cell also gives you a + Post shortcut that opens the composer with that slot filled in.
You can move anything that hasn't gone out yet — scheduled, waiting for approval, or a draft. You can't schedule into the past.
How close to the scheduled minute does it actually publish?
xpost looks for due posts every minute, so a post normally leaves within about a minute of its time.
After that it's the platform's clock, not ours. Some platforms accept a post immediately and publish it a moment later — those sit as in flight on Receipts until the platform confirms, which is the receipt turning green rather than us guessing.
Why is my post sitting in Approvals?
Because an AI agent wrote it and the project is in copilot mode — the whole point of it. Anything created through the API or an MCP connector with an agent key waits for a human before it can publish.
Posts you write yourself are never held, and drafts are never held. If you'd rather your agent publish unsupervised, switch the project to autopilot under Project settings → Agent.
Still stuck? Ask a person.
Email support@xpost.to. If it's about a post that went wrong, the fastest thing you can send is the link to it from Receipts — that page already has the platform's own error text on it.
Building on the API or wiring up an agent? The developer docs go deeper than these pages do.