> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate a run

> Inspect an existing workload execution without starting replacement work. Enter its workload ID and run ID under Example values.

How-to guideApplies to: Unified engine deployments

Inspect an existing workload execution without starting replacement work. Enter its workload ID and run ID under Example values.

### Investigate a workload run

Set an existing workload ID and run ID. These requests inspect execution and notification delivery without starting another run.

| Placeholder | Value |
| - | - |
| `{{workload_id}}` | Your environment value. |
| `{{run_id}}` | Your environment value. |

Replace the placeholders in your client. Keep returned IDs for later requests. Paths below use the native API prefix; adjust it for your deployment.

#### 1. Read the run

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/workloads/{{workload_id}}/runs/{{run_id}}
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/get-run.md).

#### 2. Read tasks

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/workloads/{{workload_id}}/runs/{{run_id}}/tasks
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/list-tasks.md).

#### 3. Read delivery history

```http theme={"theme":{"light":"github-light","dark":"github-dark"}}
GET /api/v1/workloads/{{workload_id}}/runs/{{run_id}}/notifications
Host: <ENGINE_HOST>
```

[Endpoint reference](https://docs.e6data.com/transformation/http/reference/notification-history.md).

Read the recorded invocation and state. Compare revision, parameters, data window, queue reasons, and task attempts. A current editor definition can differ from the version recorded by the run.

Notification history is separate from data execution. An exhausted delivery does not turn a successful workload into a failed one. Use delivery retry to resend an event; use selective rerun to repeat eligible tasks.

For a write with an uncertain outcome, keep the original identities and inspect commit evidence. Do not create a fresh append because the browser lost its response.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.