Automation Run Log and Retry
Every automation rule stores its execution history. You can see exactly when a rule ran, which lead it affected, and whether an error occurred.
Opening the logβ
- Open Automations in the sidebar.
- Each rule card shows a Recent runs section at the bottom.
- Up to 50 runs are shown per rule, newest first.
Understanding statusesβ
| Status | Colour | Meaning |
|---|---|---|
| Success | Green | All actions executed successfully |
| Error | Red | At least one action failed |
| Dry run | Blue | Simulation β no real actions executed |
| Skipped | Yellow | Conditions not met, no action needed |
Reading error textβ
When status is Error, the error text is shown directly below the timestamp. Common causes:
- No AI key configured β check BYOK configuration under Integrations
- Slack webhook unreachable β verify the webhook URL in workspace secrets
- Lead no longer exists β lead was deleted in the meantime
Retrying a failed runβ
- Find the failed entry (red badge).
- Click Retry on the right side of the entry.
- The system creates a new run for the same lead and rule.
- Check the result in the log.
Using dry runsβ
The Dry run button per rule simulates execution:
- Shows how many leads match the conditions.
- Executes no real actions.
- Creates an entry with status Dry run in the log.
Use dry runs before activating a new rule.
Tipsβ
- Keep automation rules focused: one condition, one action.
- Monitor the log actively after the first real run.
- For frequent errors, check the integration configuration under Integrations β AI or Slack.