How-to
Automation runs and stats
Follow an automation's runs, read the overview and per-step statistics, cancel runs, debug failed runs, and fetch runs and stats with the API.
Every time a trigger fires, the automation creates a run. This page shows where to see runs and their results, what the statistics on each step mean, how to cancel a run, how to find out why a run failed, and how to do the same with the API.
Overview tab
Open an automation from Email MarketingAutomations. The Overview tab shows:
- Total executions, Completed, Failed and Running counts.
- A read-only diagram of the flow. Select any step to see its Stats.
- Edit, which opens the editor while the automation is a draft or paused.
While the automation is running, the numbers refresh every 10 seconds.
Step stats
Each step’s Stats count how many runs reached it and what happened there. What you see depends on the step:
| Step | Stats |
|---|---|
| Send email | A funnel of Accepted, Delivered, Opened and Clicked, each as a share of accepted emails, plus counts of Bounced, Failed, Complained and Unsubscribed. The counts follow each email after the step sent it. |
| Condition (If/Else) | Matched (the run took Yes) and Not matched (it took No). |
| Webhook | 2xx Success, 4xx Client Error, 5xx Server Error, Timeout and Network Error. |
| Random split (API) | Runs per variant. |
| Every other step | Runs per status, such as Completed, Waiting, Skipped and Failed. |
Opened and Clicked count when the sending domain tracks loads and clicks. Marketing emails skipped for unsubscribed contacts have the outcome skipped. A Wait until step’s outcomes are matched and timeout, and a Goal’s reached and not_reached.
Runs tab
The Runs tab lists every run, newest first, with its Status, the Event that started it, the Contact, a Note saying why a canceled run stopped, and when it Started and Completed, with the Duration. Filter by status, event or creation date.
Select a run to see its details: its status, start and end times, what it’s waiting for, and each step it went through, in order, with the step’s status, outcome and duration. Expand Output data on a step to see what it returned, such as the ID of the email it sent, the branch a condition took or the error that made it fail.
| Run status | Meaning |
|---|---|
| Running | Working through its steps, or waiting in a Time delay or Wait until step. |
| Completed | It reached the end of its path or an End automation step, or moved to another automation. |
| Failed | A step failed, or the workspace didn’t have enough credits to start the run. |
| Canceled | It stopped early. The Note says why: Met an exit condition, Left the audience, Canceled by a user, Removed with the API, Removed by another automation, Automation stopped or Contact deleted. |
Steps skipped because the run jumped to a goal show as skipped.
Cancel a run
To take one contact out of an automation, open their run on the Runs tab and select Cancel run. Its waiting steps are canceled and no more steps run. Canceled runs can’t be resumed; a new trigger starts a new run.
With the API:
- Cancel a run:
POST /v2/automations/{id}/runs/{run_id}/cancel, with an optionalreason. - Remove a contact from an automation:
POST /v2/automations/{id}/exitwithcontact_idoremailcancels every run of that contact in the automation, for example from your shop when an order is paid. - List a contact’s runs:
GET /v2/automations/runs?email=…shows which automations a contact is in.
To do this automatically, use exit conditions instead.
Debug a failed run
-
Find the failed runs. On the Runs tab, filter by Status
failed. -
Open a run. The failed step is marked in red.
-
Read the error. Expand Output data on the failed step. The
errorfield says what went wrong, for examplesend_email: Sending domain is not verified or not found. See When a step fails for common errors and their fixes. -
Fix the cause. For a step setting, select Pause, correct the step on the Editor tab, select Save and then Start. For a workspace problem, such as missing credits or an unverified domain, fix it under Workspace or Email API.
A failed run with no steps usually failed because the workspace didn’t have the 3 credits needed to start it. With the API, its meta shows "failure_reason": "insufficient_credits". Top up credits or turn on auto-refill so runs don’t fail.
Failed runs aren’t retried. New triggers start new runs as usual. To run the automation again for a contact or email that failed, fire its trigger again, for example by removing the contact from the audience and adding it back.
A run that stays Running for a long time is usually in a Time delay or Wait until step. Open it to see which step it’s on and what it’s waiting for.
Use the API
List runs returns an automation’s runs, newest first. Filter with filter[status] (running, completed, failed or canceled) and filter[contact_id], and page with page and per_page (up to 100):
curl -G "https://api.emailit.com/v2/automations/aut_3Mv8Xq2nKp5Lt/runs" \
--data-urlencode "filter[status]=failed" \
--data-urlencode "per_page=25" \
-H "Authorization: Bearer $EMAILIT_API_KEY"{
"data": [
{
"id": "aur_7Kp2Vx9mQt4Lw",
"automation_id": "aut_3Mv8Xq2nKp5Lt",
"contact_id": "con_2kq8Vt4xLm7Rz",
"email_id": null,
"event_id": null,
"event": "contact.added_to_audience",
"payload": { "object": { "id": "sub_7Rt2vX9kLm3Qp", "object": "subscriber" } },
"meta": { "source_event_id": "evt_2Hn6Wq8rTc3Mz" },
"status": "failed",
"cancel_reason": null,
"started_at": "2026-10-01T09:30:00Z",
"completed_at": "2026-10-01T09:30:02Z",
"created_at": "2026-10-01T09:30:00Z",
"updated_at": "2026-10-01T09:30:02Z"
}
],
"total_records": 1,
"per_page": 25,
"current_page": 1,
"total_pages": 1
}Retrieve a run adds run_steps, with each step’s step_id, step_key, action, status, outcome, data (the output, including any error), started_at and completed_at, and waits, the Wait until and Goal steps the run is or was waiting in, with what they wait for (kind, event), their status and timeout_at.
Retrieve statistics returns the stats of every step, keyed by step key. Narrow them with since and until (ISO 8601) or run_ids[]. Retrieve step statistics returns one step’s stats:
{
"data": {
"send_email-1": {
"total": 120,
"by_status": { "completed": 118, "failed": 2 },
"by_outcome": { "accepted": 5, "delivered": 58, "loaded": 43, "clicked": 9, "bounced": 3, "error": 2 },
"funnel": { "accepted": 115, "delivered": 110, "loaded": 52, "clicked": 9, "bounced": 3, "failed": 0, "complained": 0, "unsubscribed": 0 }
}
}
}by_status counts how the step ended in each run. by_outcome counts its results, such as the latest status of the email it sent or matched and not_matched for a condition. funnel appears for Send email steps.