Why My Automation Was Skipped

When an automation seems to have skipped a conversation, the answer is almost always in the Logs. Here is how to read them and what to look for.

When to use this guide

Whenever you expected an automation to run but nothing happened.

Before you start

• Admin access to view automation logs.

Step-by-step

1. 1

   Open the automation logs

   Automation → click the automation → Logs tab. You'll see one row per evaluation, with status: Ran, Skipped, or Failed.

2. 2

   Confirm the trigger fired

   If the conversation isn't in the log at all, the trigger never matched. Common cause: the trigger is 'Tag Added' but the tag was added before the automation was activated.

3. 3

   Read the Skipped reason

   Skipped rows show which condition blocked the run, e.g. 'Source != Instagram' or 'Outside business hours'. Adjust the condition or the source data and re-test.

4. 4

   Check the activation toggle

   An inactive automation never runs. Confirm the Active switch is on at the top right.

5. 5

   Check your plan's automation limits

   Some plans cap the number of monthly automation runs. If you've hit the limit, Logs will show 'Skipped: plan limit reached'. See Usage Limits Explained.

6. 6

   Re-run on a sample input

   Click Test → paste or pick a sample event. The Logs will show step-by-step what would happen, including which condition passes or fails.

What happens next

Once you fix the trigger, condition, or limit, the next matching event will run normally. Old missed events do not re-run automatically.

Common issues