When a post doesn't go out
Expired sign-ins, failed and partial deliveries — and what fixes each.
- Why won't it let me post more to Instagram or TikTok today?
- A post failed. What now?
- It says the post was 'partial'
- Pinterest refused my pin because of its link
- An account says its sign-in expired
Why won't it let me post more to Instagram or TikTok today?
Those two platforms cap how much one account may publish in a day, so xpost throttles before they do: 100 posts per Instagram account and 15 per TikTok account in any rolling 24 hours. These aren't settings — they're the platforms' rules.
A new post that would go over the cap is refused when you create it, so you know before it's scheduled. If a post was already scheduled when the cap filled up, it isn't failed straight away: the row says Waiting and it retries every five minutes without burning an attempt. If the cap still hasn't cleared an hour after its slot, it's marked failed as a missed window, and you pick it a new time.
A post failed. What now?
Open Posts → Needs you and click the post. There's one row per account saying what went wrong in plain words, with the platform's own error text kept alongside — not a generic 'something went wrong'. Anything that reached some accounts but not all is on that tab too.
xpost tries up to three times — waiting half a minute after the first miss, a couple of minutes after the second — before it calls a delivery failed, so while a row says Retrying… there's nothing for you to do. Two exceptions: a refusal the platform calls permanent fails on the first try, and a delivery still failing an hour past its slot isn't retried any more.
The two common causes read differently: sign-in expired means reconnect the account (see below) and post again; anything else is usually the platform rejecting the content — a video too long, a missing image, a caption over the limit. What each platform accepts covers most of those.
It says the post was 'partial'
Some accounts got it, some didn't. Every account is delivered to independently, so a broken connection on one platform doesn't hold up the rest.
The post's page shows you which ones landed and which didn't. A failed row carries Try again, which re-sends to just that account — or Fix and send again when the content was the problem, which opens the composer with only the failed accounts ticked. The successful ones stay put and won't be duplicated.
Pinterest refused my pin because of its link
Pinterest checks the address a pin opens against its own spam list, and refuses the whole pin when the address is on it — the row on the post's page says the link may lead to spam, in Pinterest's words. It is the link it objects to, not the picture or the title, and it is a verdict about the domain, not about you.
Sending it again won't change that, so xpost doesn't retry it. Take the link out, or point it at another page, and use Fix and send again on the failed row — the other networks already have the post and won't get it twice.
If the blocked address is your own site, claim it with Pinterest at pinterest.com/settings/claim, or ask them to review it through their help centre. Claimed sites are rarely blocked.
An account says its sign-in expired
Platforms expire their access sooner or later, usually after a password change or a permissions change on their side. xpost checks every connected account on a schedule — every few minutes — rather than waiting for a post to fail, so you normally see this before it costs you a post: a red dot on Social accounts in the sidebar and a red panel on the account's row explaining what broke.
The fix is to reconnect that account on Accounts: broken accounts sort to the top, and the row grows a Reconnect button beside its menu. There's nothing to press to re-check — the scheduled check keeps every row current on its own.
Where a platform tells us in advance, you get the warning early: when an account's access has a known end date, we try to renew it quietly, and if we can't we email you about three days out — once, not every day — so you can reconnect before anything scheduled misses. Those emails are the An account needs reconnecting switch under Project settings → Notifications.
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 Posts → Needs you — 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.