Documentation Index

Fetch the complete documentation index at: https://resend.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Every time an event triggers an Automation, Resend creates a run. A run tracks the execution of each step in the workflow, including its status and timing, along with any errors.

[​

](#how-it-works)

How it works

Each run has one of the following statuses:

[​

](#skipped-steps)

Skipped steps

When a contact unsubscribes, any remaining Send Email steps in the Automation will be skipped automatically. Other step types (such as Delay, Condition, Update Contact, etc.) will still be executed as normal.

[​

](#listing-runs)

Listing runs

Using the dashboard

Navigate to the Automations page and select an Automation to view its runs.Each run shows:

• Status — Whether the run is running, completed, failed, cancelled, or skipped.
• Started — When the run began.
• Duration — When the run finished (if applicable).

Using the API

List all runs for an Automation:

Response:

{
  "object": "list",
  "has_more": false,
  "data": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "status": "completed",
      "started_at": "2026-10-01 12:00:00.000000+00",
      "completed_at": "2026-10-01 12:05:00.000000+00",
      "created_at": "2026-10-01 12:00:00.000000+00"
    }
  ]
}

View the List Automation Runs API reference for more details.

[​

](#filtering-runs-by-status)

Filtering runs by status

• Using the dashboard

• Using the API

[​

](#viewing-a-single-run)

Viewing a single run

• Using the dashboard

• Using the API

View the Retrieve Automation Run API reference for more details.

[​

](#debugging-failed-runs)

Debugging failed runs

• Using the dashboard

• Using the API

When a run fails, use the step-level details to identify the issue:

1. List failed runs: Filter runs by status=failed to find problematic executions.
2. Retrieve the run: Get the full run details including the steps array.
3. Find the failed step: Look for the step with a failed status.
4. Check the error: The error field on the failed step contains details about what went wrong.

Common failure scenarios:

• Condition error: A referenced field may not exist in the event payload. See Condition for how conditions are evaluated.
• Wait for event timeout: The expected event was not received within the timeout window.
• Send email failed: The template may not be published, or the sender address may not be verified.

[​

](#stopping-an-automation)

Stopping an Automation

• Using the dashboard

• Using the API

View the Stop Automation API reference for more details.

[​

](#viewing-metrics)

Viewing Metrics

In the dashboard, you can view overall metrics for any Automation. In the Observability panel for any Automation, select Metrics. The API currently does not support fetching metrics for an Automation.