How to troubleshoot Instagram automation delivery

Fast checks

• Confirm the automation is active, not draft or archived.
• Confirm the connected Instagram account is still connected.
• Check whether the trigger is watching the right post, Reel, story, or account.
• Check the keyword spelling and whether the comment actually matches.
• For normal DMs, check the 24-hour messaging window. For a comment private reply, check the separate seven-day one-time reply window.
• The first comment private-reply step must contain one text, image, or audio block. Move extra blocks to a later Send Message step; do not add placeholder text before audio. If a later step is waiting, the person needs an open 24-hour DM window: a reply or qualifying quick reply or message button opens it; a website-link click does not.
• Check whether the Link or destination is active.

Common causes

• The comment used a word you did not include.
• The automation is set to selected content and the post was not selected.
• The user already triggered the flow and the workflow is waiting on another step.
• A manual reply or pause setting stopped automation for that contact.
• The connected account needs refreshed permissions.
• A delay pushed the DM outside Meta's allowed messaging window.
• The original comment or commenter was deleted, removed, blocked, or otherwise became unavailable before Instagram sent the private reply.
• The message needs review because an AI step or confidence rule held it back.

Pending after a comment spike

Pending is expected when a post gets a rush of matching comments. LinkStack paces private replies per connected Instagram account, then retries with backoff if Meta explicitly asks it to slow down. Open recent automation activity to see the queue reason. Do not rebuild or republish the automation just because a reply is queued; that can create more work without moving the provider limit.

• Queued replies are not counted as sent until Instagram accepts them.
• The queue keeps its place across worker restarts because the scheduled send time is stored in the database.
• Workflow steps after the private reply wait until that delivery is accepted or definitively skipped.
• If the seven-day private-reply window expires first, LinkStack skips the reply instead of sending outside Meta's rules.

Step-by-step troubleshooting

1. 1Open Automations and find the workflow.
2. 2Check status, connected account, trigger type, selected content, and keywords.
3. 3Open the workflow canvas and run validation.
4. 4Use the test tool with the exact keyword or inbound message you expected.
5. 5Check recent automation activity for a Pending reply and its Instagram queue reason.
6. 6If Activity says Comment unavailable, the event is terminal. LinkStack does not offer a retry or public-reply edit because Instagram no longer exposes the original comment or commenter.
7. 7If a message button was tapped immediately after the prompt arrived, LinkStack checks for that saved reply when the wait becomes ready and during scheduled processing. An active workflow can continue without another tap while the 24-hour messaging window remains open. If it stays waiting, check the button's connected path and recent activity.
8. 8Check the Inbox for the contact and look for pause state, manual replies, or provider window warnings.
9. 9Check Review Queue if AI or review-first replies are involved.
10. 10Open the linked Link and confirm it is active.
11. 11Retest from Instagram after saving changes.

When to rebuild

Rebuild only when the trigger or campaign idea changed. A high-volume reply that says Pending is already queued and does not need a rebuild. Most other delivery issues are setup details: wrong content, wrong keyword, stale connection, expired window, inactive link, or a message waiting for review.