Scheduling

Failures, retries and unknown outcomes

A destination that failed is known not to have published, so retry sends it again as a new post. A destination in unknown may already be live, so 1Post never retries it on its own. Check the account, then attach the live post with link-live, or duplicate the post and send it again.

Updated 2026-10-26

States of a destination

StateWhat it meansWhat to do
ScheduledWaiting for its time.Nothing. You can still change or cancel it.
PublishedLive on the network.Results are collected from here on.
FailedRefused or not sent, and known not to be live.Fix the cause, then retry.
UnknownThe network did not say whether it published.Look at the account, then link-live or duplicate.

Reconnecting

When a network stops accepting an account, the account shows as needing a reconnect and posts for it wait. Reconnect the account and its scheduled posts are kept. A webhook, account.reconnect_needed, tells your code the moment this happens.

Try it

Start a trial

7-day trial for $1. Connect your accounts and schedule a week of posts in one sitting.

Start a trial
Free in your browser

Free tools

Count characters the way each network does, split threads and preview posts. No account needed.

Open the tools
For builders

API and MCP

Post to every network from your own code or assistant with one key, signed webhooks and idempotent requests.

See the API

Get this week’s posts scheduled

Connect your accounts, write once and let 1Post publish on time while you get on with the rest of your day.