Automations
Run history & troubleshooting
Every time an automation is evaluated it writes a run. Run history is where you confirm rules are firing and diagnose the ones that are not.
Where
See a project-wide feed under Automations → Run History, or open a single automation and switch to its Runs tab.
Reading a run
| Status | Meaning |
|---|---|
completed | Conditions matched and every action succeeded. |
failed | Conditions matched but an action errored (the error is shown). |
no match | The trigger fired but the conditions did not match this lead. |
Runs are recorded even when conditions do not match, so “why didn’t my rule fire?” is answerable: if you see a no match run, the trigger reached the automation but the conditions excluded the lead.
Common fixes
| Symptom | Likely fix |
|---|---|
| No runs at all | The automation is off, or the project kill switch is on. Check the Active toggle and Settings → CRM. |
| Only ‘no match’ runs | Conditions are too strict, or the pipeline scope excludes the lead. Use the dry-run test. |
| Send action failed | Out of credits, contact opted out, or (WhatsApp) outside the 24-hour window with no fallback template. |
| No-reply rule never fires | The automations scheduler is not configured. |
| AI reply skipped | Channel not enabled, rate limit or daily cap hit, outside business hours, or no provider API key set. |