Studio checks up front that the time is in the future, the target platform is
connected, and the content fits that platform’s limit — you find out now, not at
2am when it fires.
Always send an offset (+02:00) or a Z. A bare local timestamp is ambiguous
and will be rejected or land in the wrong hour.
A cron tick runs every minute, so posts go out within roughly two minutes of the
target time. Dispatch re-validates everything against the database, then
publishes through the same path as publish_post.If it fails, the post lands in failed with a failureReason:
Why did my Tuesday post fail?
Permanent problems — a revoked connection, an expired token, a platform
rejection — fail on the first attempt. Transient ones (rate limits, platform
outages) retry with exponential backoff up to five times.Fix the cause, then re-schedule the failed post directly — no need to unschedule
it first:
Reconnect LinkedIn, then reschedule that post for tomorrow at 9am.