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 matches it.
• 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.
• Check Pause automations in Inbox and use Resume automations when ready. Older AI takeover holds appear here as pauses. Taking over or removing an AI agent ends its current work without creating a separate hold on future triggers.
• 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.

Repeated comments and DM keywords

Comment triggers allow one start per person, post, automation, and configured keyword, with no time reset. Incoming DM keyword triggers allow one start per person, automation, and configured keyword every five minutes. Extra comments and DMs are silently suppressed without an error, reply, queued send, or monthly trigger charge. This protection stays on even when the manual-reply pause setting is Off.

• Only a qualifying comment uses the post allowance. An unrelated comment does not prevent a later matching keyword. Another post or a different matching keyword has its own allowance.
• Any-comment triggers allow one start per person, post, and automation. Capitalization and extra text do not reset an allowance. If a comment or DM matches several configured keywords, it uses each matched allowance; an unavailable keyword suppresses the whole trigger.
• The five-minute DM cooldown begins when the trigger is admitted. Extra DMs do not extend the timer and will not send later. After five minutes, a new matching DM can trigger again, subject to existing pauses and active-workflow rules. Waiting five minutes does not reset a comment's post allowance.
• Messages, button taps, and scheduled steps inside an existing workflow continue normally. The original accepted delivery can still retry after a temporary failure.
• DM automations configured for any message keep their existing once-per-person behavior. Story replies keep their existing rules.

Retry a failed Inbox reply

Retry uses the saved reply and current connection, and updates the original message. It does not regenerate an AI answer, repeat AI actions, or restart a workflow. Reconnecting and resuming do not automatically resend old failures. Workflow retries remain in Activity; private comment replies and test messages do not have this Inbox control. If delivery cannot be confirmed, check the Instagram conversation before sending again.

1. Open the conversation in Inbox and read the error under the failed reply.
2. Reconnect under Settings → Integrations if the account is disconnected. For an AI reply, confirm the agent is active and the messaging window is still open. Automation pauses do not block AI replies. An explicit contact stop request still stops the agent; assigning an agent again restarts it.
3. Choose Retry message beside the failed direct reply. Wait for the retry to finish and check its status or error.

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 waits longer between retries if Meta 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; it does not change Meta's sending limit.

• Queued replies are not counted as sent until Instagram accepts them.
• The trigger's public confirmation also waits for a successful DM. A failed or skipped DM does not post a public reply saying it was sent.
• If Instagram explicitly rejects the public confirmation with a temporary server error, it stays Pending and retries after one, five, and fifteen minutes. Only the public reply is retried; the DM and completed workflow are not repeated. If all three retries fail, inspect the error in Activity. Older failed public confirmations can also use Activity's Retry control when eligible.
• An unavailable comment, permission failure, or uncertain provider response does not trigger these automatic retries. Check Instagram before retrying an uncertain send.
• A manual contact pause also holds unsent queued workflow replies. They recheck about once a minute without consuming additional sending capacity, and later steps wait.
• Queued replies survive temporary interruptions. When sending resumes, overdue replies still send at the account's normal pace; they do not all send at once just because their scheduled times have passed.
• 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. Open Automations and find the workflow.
2. Check status, connected account, trigger type, selected content, and keywords.
3. Open the workflow canvas and run validation.
4. Use the test tool with the exact keyword or inbound message you expected.
5. Check recent automation activity for a Pending reply and its Instagram queue reason.
6. Choose Skipped activity to review skipped triggers and sends that need attention. If the same workflow is already waiting for that person, repeat triggers are silently skipped and do not appear in Activity. Check the original run instead. The skipped repeat sends no duplicate reply and will not retry automatically. Replay is available only for eligible delivery records.
7. If 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.
8. If 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.
9. Check the Inbox for the contact and look for pause state, manual replies, or provider window warnings.
10. If Activity offers a retry for a failed message, it sends only that message. The original failed or completed workflow stays stopped. Cancelled or expired workflows remain blocked, and the retry still needs an active automation, connected account, unpaused contact, and eligible messaging window.
11. Check Review Queue if AI or review-first replies are involved.
12. Open the linked Link and confirm it is active.
13. Retest 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.