# Troubleshoot an automation

> Find why a workflow did not run, stopped at a step, or paused.

_Collection: AI & Automation (ai-automation) — Kepler Help Center. Canonical: https://keplercrm.com/support/articles/troubleshoot-automations/_

These checks apply where Automations is enabled. Start by opening the automation and checking its status, then open **Runs** for evidence of what happened.

| What you see | What to check next |
| --- | --- |
| No run appears | Check that the automation is live and published. Confirm that the event and record match the trigger's conditions. A saved draft or unpublished change is not the version that runs. |
| A test runs no steps | Check the sample record shown in the Test panel. A record that does not match the trigger produces no steps. Adjust the filters if they exclude records you intended to include. |
| A failed or forbidden step | Open the run and read the step's explanation. Check the selected record, required configuration and the author's permissions shown by Runs as in Settings. Correct the draft and test before republishing. |
| A waiting run | Inspect its steps for the configured wait. If the work should stop, cancel that waiting run from its details. |
| The automation paused | Review recent failures. Settings includes Pause after N failed runs in an hour . Resolve the cause before resuming; changing this setting alone does not fix a failed action. |

Pausing or archiving cancels waiting runs. Resuming allows the workflow to handle new matching events; it does not restore cancelled runs. If you still need help, share the automation name, the affected run and the step's error with your administrator or Kepler support.