Run history & re-run

Every time an automation looks at a lead, a run is kept: Delivered (it did its job), Filtered (a rule stopped it, and the run names the rule) or Failed (something went wrong, and the run shows the reason). Fix the cause, then retry.

1. View runs on an automation's card. The card itself shows the last 7 days: Successful / Filtered / Failed.
2. Failed shows what went wrong for each lead: company, result, when.
3. Retry this lead, or select several and Retry N leads.

Common questionsCopy Anchor Link

What do Delivered, Filtered and Failed mean? Delivered: the lead reached Slack, your CRM, the webhook or the campaign. Filtered: the lead did not match a filter rule or the frequency (for example a returning visitor on Only the first time); nothing was sent and nothing is wrong. Failed: we tried and the other side refused (a disconnected CRM, a webhook URL that errors, an archived Slack channel).

Why didn't my automation run for a lead? Open the lead's row in the run history or the Automations column on the Leads page. A Filtered run names the rule; no run at all means the automation was paused, a draft or saved after the lead arrived. Build an automation explains how to run it on older leads.

How do I retry a failed one? Fix the cause first (reconnect the integration, fix the URL), then Retry this lead. The retry is a real send to the same destination.

Can I retry many leads at once? Yes. Tick the runs (Select all loaded runs or Select all N matching) and click Retry N leads; it runs in the background. You can also tick leads on the Leads page and use Retrigger, choosing which automations to run and whether to include leads that already succeeded.

How do I see which automations ran for one lead? On the Leads page, the Automations column and the lead's panel list every automation that ran for it and the result.

Can I export the run history? Yes, Export CSV in the run history panel.

Every control on this screenCopy Anchor Link

Every button, field and switch, with what it does.