AP3K stores delayed deliveries, scheduled follow-ups and waiting flow sessions so eligible work can continue later. There is no separate In queue panel in the AP3K sidebar.
What waits for delivery?
A configured delay waits until its due time. A follow-up waits for its schedule and conditions. A collection step waits for the contact’s reply. These are different reasons for a message not appearing immediately.
Immediate and scheduled messages
Do not assume every immediate message passes through a visible account-wide queue. Scheduled work is stored durably and processed by delivery workers or the scheduler. Eligibility is checked again when it resumes.
What can stop a waiting message?
- The automation is inactive or archived.
- The Instagram connection requires attention.
- The contact or conversation no longer meets the conditions.
- The reply window has expired.
- An API or delivery error prevents sending.
Stored work is not a guarantee of eventual delivery. Expired or ineligible work can be cancelled, and ambiguous failures are not blindly replayed.
Check delivery
Review the automation status, the recipient’s Inbox conversation and account connection. For delay-specific checks, see Delay node. For general problems, see Automation not working.