Why an automation did not trigger

Start with one fresh test

The preview shows a prepared conversation; it does not create an Instagram event. Test a real comment or incoming message from another account after saving and enabling the rule. A repeated delivery of the same event is processed once. Refreshing the page or toggling the rule does not replay it.

Check the rule conditions

1. In Settings, verify the connected professional account and current permissions. If the connection needs attention, complete the Meta login again.
2. In the editor, check that the automation is enabled, then check its trigger, selected post or Story, and keyword. Matching ignores letter case and accents; it can find the keyword within a longer message.
3. Review other enabled rules. When several rules match one event, DMFLOW uses the first in creation order, rather than starting all of them.
4. Check the sending history. An existing queued, expired, or uncertain job points to a different problem from an event that never started a run.

When no events arrive

The deployment owner needs to check the account's webhook subscription, app permissions, and server permission for live sending, LIVE_SENDS. This is separate from the preview. Meta development mode can limit access to accounts with the required role; a connection alone does not prove production app access.

A comment also needs a verified creation time within the seven-day private-reply window. Ordinary DMs depend on an incoming message within the last 24 hours. Avoid duplicating a rule to bypass duplicate protection. Use a fresh eligible test instead.