# Run history & re-run

> See what each automation did with each lead, and run it again once a failure is fixed.

Every section below does the same job: in the dashboard (Guide), from your code (API) or through an AI assistant (MCP).

## Guide — In the dashboard

Source: /docs/automations/run-history

Every run is kept: delivered, filtered out (with the rule that stopped it) or failed (with the reason). Fix the cause, then retry.

<DemoFrame guide="automations-run-history" to="/automations/{workspace}" />

1. **View runs** on an automation.
2. **Failed** shows what went wrong.
3. **Retry this lead**, or retry several at once.

### Every control on this screen [#every-control-on-this-screen]

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

<ScreenControls screens={["automation-runs"]} />


---

## API — From your code

Source: /docs/automations/run-history/api

Authenticated with `?privateKey=YOUR_KEY` (see [Authentication](/docs/authentication)).

<Endpoints ops={["POST /admin/automations/re-trigger", "POST /admin/automations/rerun-single", "GET /v3/leads/{leadId}/automation-history", "GET /v3/automations/{automationId}/runs"]} />

<ApiPlayground
  ops={["POST /admin/automations/re-trigger", "POST /admin/automations/rerun-single", "GET /v3/leads/{leadId}/automation-history", "GET /v3/automations/{automationId}/runs"]}
  method="get"
  path="/v3/leads/{leadId}/automation-history"
  tool="get_lead_automation_history"
  args={`{
  "leadId": ""
}`}
/>

### Use case: Retry after a fix [#use-case-retry-after-a-fix]

`POST /admin/automations/re-trigger` with the `leadIds` and `automationIds` to run again.


---

## MCP — AI agents

Source: /docs/automations/run-history/mcp

Connect the [MCP server](/docs/mcp#quickstart), then just ask.

<Tools names={["get_lead_automation_history", "retrigger_automations", "rerun_automation_for_lead", "get_automation_runs"]} />

### Use case [#use-case]

> Why wasn’t this lead sent to HubSpot?

<McpToolCall name="get_lead_automation_history">

```json
{
  "leadId": "6530c1d2e3f4a5b6c7d8e9f2"
}
```

</McpToolCall>