> ## 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.

# Inspect runs and attempts

> Follow the recorded execution rather than assuming the current editor represents what an earlier run used. A run connects the saved revision, parameter values, schedule trigger, ta

How-to guideApplies to: Unified engine deployments

Follow the recorded execution rather than assuming the current editor represents what an earlier run used. A run connects the saved revision, parameter values, schedule trigger, task states, and attempts.

## Find the run identity

Open the workload's run history and select a run. Record its workload ID, run ID, revision, trigger, scheduled time, and effective parameters. For windowed work, also record the data window. Selective reruns and backfills add their origin or backfill identity.

The editor can contain a newer revision. When using a current-definition graph or code view, compare it with the run's recorded invocation before drawing conclusions.

## Follow tasks

Use the timeline to compare phases and durations. Open a task to inspect attempts, failures, execution settings, and commit evidence. A retry adds an attempt to the existing task run; it does not create another workload run.

| Task state | What to inspect |
| - | - |
| Pending | Unmet predecessors or work that has not entered execution. |
| Planning | Query planning and input preparation. |
| Queued | Admission reason and queue deadline. |
| Provisioning / WaitingWorker | Allocation, selected profile, and worker readiness. |
| Running | Active execution, or a sensor's saved wait details. |
| Committing | Publication progress and commit evidence. |
| WaitingRetry | Last failure, retry eligibility, and saved delay. |
| Succeeded | Confirmed task completion; inspect a write's commit separately. |
| Failed | Final failure after applicable retry rules. |
| Skipped | A dependency or execution decision prevented the task from running. |
| Cancelling / Cancelled | Stop progress and the final known effects. |
| OutcomeUnknown | The final outcome is not confirmed. |

A sensor can be Running without holding a SQL compute worker. Read its check count, next check time, deadline, and last observation.

## Compare runs

Compare revision, supplied and effective parameters, context, windows, compute, and task attempts. Identical names do not imply identical execution settings. A reused task in a selective rerun should show its source run rather than a new execution attempt.

For the [first workload](https://docs.e6data.com/transformation/workloads/first-workload.md), two runs of the same revision should calculate the same six-order total. Editing the query should produce a later revision while earlier invocation records remain intact.

## Control future and active work

| Goal | Action |
| - | - |
| Stop new run creation | Pause the workload. |
| Stop one active run | Request run cancellation and follow its final state. |
| Execute the current definition again | Start a new run or use Run again. |
| Repeat selected work from a recorded run | Preview a selective rerun. |
| Process historical windows | Preview a backfill. |

Use **Rerun tasks** on a completed run to preview selective execution. Use the workload's **Backfills** tab for historical windows, and **Notification history** on a run for delivery attempts. These actions have different identities and do not replace each other.

Run cancellation is available through POST `/api/v1/workloads/{workload_id}/runs/{run_id}/cancel`. Cancellation requests a stop; it does not undo confirmed writes. Pausing does not cancel active work, and cancelling one run does not pause the schedule.

Closing the browser does not stop engine execution.

## Inspect results and diagnostics

Run and task pages focus on execution. Use retained result APIs or query the destination in Workbench for rows. Read [Results and table commits](https://docs.e6data.com/transformation/workloads/results-and-commits.md) for publication checks.

Use [Observability](https://docs.e6data.com/transformation/operations/observability.md) for instance-wide metrics, and [Troubleshooting](https://docs.e6data.com/transformation/workloads/troubleshooting.md) to choose the next action for a specific symptom.


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