Automation Not Running

An automation that is not running is one of the most common issues Chase Agents users encounter. This guide walks through the most likely causes in order of frequency.

1. The Automation Is Disabled

Check first whether the automation is enabled. In the automations list, enabled automations show a green status indicator. Disabled automations have a grey or off indicator. Click the automation and toggle it to enabled if it is off. Automations can be automatically disabled when plan limits are hit, when auto-fix fails to repair a repeated error, or when you manually disabled it and forgot to re-enable it.

2. Plan Action Quota Exhausted

If your workspace has used all of its monthly action quota or exhausted its trial actions, automations will not execute their connection steps. Check your usage in Workspace Settings. If you are on the Starter trial with 50 actions, these are consumed quickly during testing. Upgrade to a paid plan to restore execution.

3. Schedule Configuration Issue

For Cron-triggered automations, verify the cron expression is correct. A common mistake is using an expression that has already passed for the current period, or an expression with an off-by-one error. The automation editor shows the next scheduled run time after you save the schedule; confirm this matches your expectation. Also verify that the schedule is set to the correct timezone.

4. Webhook Not Being Sent

For webhook-triggered automations, verify that the source system is sending requests to the correct Chase Agents webhook URL. Check whether the source system's webhook delivery logs show successful sends or errors. Also confirm the webhook payload format matches what your automation expects. Run the automation manually with a sample payload from Workflow History to verify the automation itself works; this isolates whether the issue is the automation logic or the webhook delivery.

5. Rate Limit Reached

Chase Agents limits each automation to 5 executions per 5-minute window. If a webhook is firing more frequently than this, excess executions are queued rather than dropped. If you see runs appearing with a significant delay, the automation may be rate-limited. Check Workflow History to see if run start times show a 5-minute pattern, which confirms rate limiting is the cause.

6. Active Automation Limit

Your plan limits how many automations can be active simultaneously. On the Starter plan, only 1 automation can be active at a time. If you have hit this limit, newly created automations may be created in a disabled state. Disable unused automations or upgrade to a plan with a higher active automation limit.

7. No Runs in Workflow History

If the automation appears enabled and the trigger should have fired but there are no recent runs in Workflow History, the trigger may not be reaching the automation. For scheduled automations, verify the next run time shown in the editor is in the future. For webhook automations, check the webhook URL is correct and the source is sending to it. Try running the automation manually to confirm it can execute.

Still Not Running?

If you have checked all of the above and the automation is still not running, post in the Chase Agents Discord with the automation name, its trigger type, what you have already checked, and any relevant Workflow History entries. The team can investigate platform-level issues that may not be visible from the workspace interface.