Triage an Instagram Automation Incident by Failed Stage

Collect the minimum context needed to reproduce the issue, including the campaign and approximate interaction time. Avoid posting private message content or credentials in a broad incident channel. Keep successful and failing cases separate.

1. 1Step 1Confirm the intended account and campaign.
2. 2Step 2Inspect the available activity around the reported interaction.
3. 3Step 3Change one likely cause and repeat a supported new test.

If the DM arrives but the button fails, investigate the destination. Reconnecting Instagram or broadening the keyword would not address that stage.

Do not assume every missing reply is a provider outage. Check scope, activation timing and the actual configured action before escalating.

Operational clarity makes a small automation library easier to maintain than a large collection of unexplained campaigns. Keep account ownership, campaign purpose and destination responsibility visible. In AP3K, review the selected account, trigger scope and enabled actions before activation, then inspect a real supported test. Use authorized access and preserve useful audit context when changing or retiring workflows.

Record the failed stage, corrective action and verification result. Repeated incidents at one stage deserve a targeted process improvement.

• The campaign has a clear purpose and responsible owner.
• Changes include a test and a record of the intended behavior.
• Unresolved incidents and paused workflows have a next action.

Use the next guide for a related decision, or browse the topic library to choose a different workflow.