When you schedule a post, AeroReply saves a snapshot of it and creates one delivery per platform. Each delivery runs on its own, so a problem on one platform never holds up the others.
The pipeline
0 of 0 done
- Snapshot. The caption and media are frozen at the moment you schedule. Editing the draft later updates the scheduled copy too.
- Dispatch. A scheduler checks for due posts every 60 seconds and queues one job per platform.
- Pacing. Jobs are paced to each platform's rate limits, so a busy minute never trips a platform's throttling.
- Validation. Before sending, the media is checked against the platform's limits. A file that no longer fits fails with a clear reason.
- Publish. The platform receives the post. Its response is stored on the delivery.
Retries
A temporary failure, such as a timeout or a platform outage, is retried automatically up to 5 times with exponential backoff starting at 5 seconds. A permanent failure, such as a revoked permission or media the platform refuses, stops straight away so you can fix it.
Post status
- Published: every platform accepted the post.
- Failed: at least one platform failed after its retries. The queue shows the error each platform returned.
When every platform has finished, AeroReply sends a post.published or post.failed webhook so your own systems can react.
Was this helpful?
Ship on-brand posts in minutes
Back to documentationAI content, scheduling, engagement and a full marketing suite — free to start.
Start free
