When an AP3K step is scheduled for later, its due time and state are stored before processing pauses. A worker resumes eligible work when it becomes due.
The trip a scheduled message makes
- An interaction matches an active automation.
- A delay or follow-up creates waiting work.
- A worker claims that work when it is due.
- AP3K checks that the automation, account and conversation are still eligible.
- The message is sent, cancelled or marked failed according to the outcome.
Two kinds of waiting
Waiting for time: a delay or follow-up has not reached its due date. Waiting for a person: a flow needs an answer or button interaction before it can continue. Neither means that the message is ready to send immediately.
Timing and recovery
A saved due time is a minimum wait. Worker availability and scheduler cadence can add latency. Durable state allows recovery after an interrupted worker, but AP3K avoids automatically replaying an ambiguous external send that might duplicate a DM.
Messages can expire
Instagram’s reply window still applies. Expired flow sessions are cancelled, and delayed jobs may be cancelled when the conversation has moved on or the automation is no longer active. There is no promise that a queued message waits forever.
Common questions
Can I buy faster delivery? A subscription does not bypass Instagram’s limits.
Where is the queue count? AP3K does not expose the source site’s In queue panel or account-wide messages-per-minute readout.
How do I investigate a missing message? Check the Inbox, active automation, selected account, configured wait and any connection or publishing error.