Each time a workflow processes recordings, it creates a run. The run page shows every step live on the graph, with its logs and the files it wrote, so nothing is a black box. When something fails, you can see exactly where and why.
Find a run
Open a project's Workflow page: recent runs are at the bottom, and View all runs opens the full list. A run's title tells you what started it, such as Run after upload or Run on selected recordings. To start one yourself, use Run workflow in the run list.
Read the run page
The top line gives the overall status and a summary, for example "1 of 1 recording succeeded" with the processing time and how long the run waited in the queue. When processing has finished, a banner offers Create version to turn the episodes into a dataset version.
Below that, Steps on the left lists every step with its status, how many items it finished and how long it took. The graph shows the same steps, each with a progress bar. Recordings at the bottom has one row per recording and one column per step, and you can filter it by Status, Step or Failure class.
Open a step
Click a step in the list. Its panel opens on the same page: the status, how long it ran and waited for a worker, its Logs, and under Outputs the files it wrote, each with Download. Open step opens the step on a page of its own, and Summary at the top of the list takes you back to the graph.
What the statuses mean
| Status | Meaning |
|---|---|
| Queued, Running | Not finished yet. A queued step may be waiting for a team slot or a free GPU, and it says which. |
| Succeeded | The run or step finished and did its job. This is the only green status. |
| Completed with warnings | The run finished, but not every step succeeded. Open the steps to see what was skipped or failed. |
| Failed | A step failed. Open it to read the cause and what to do next. |
| Cancelled | Someone cancelled the run. Finished steps keep their logs and outputs. |
| Cached | The step reused the result of an earlier run with the same input and settings. |
| Skipped | The step didn't run, and it says why: a condition wasn't met, an earlier step failed, or a test window saves nothing. |
| Not applicable | The recording doesn't have what the step needs, for example a stereo pair. |
Only Succeeded is a pass. Skipped, not applicable, not evaluated and error are shown in grey or red, never as success, and a run that contains one of them reads Completed with warnings rather than green.
Reuse, retry and rerun
Runs reuse work. When a step's input and settings haven't changed, its earlier result is reused and the step reads Cached, so a second test or a rerun finishes much faster.
- Retry failed steps, on a failed run, runs the failed steps and the steps after them again. Finished steps are reused. Fix the cause first, or the retry gives the same result.
- Rerun from this step, in a step panel, runs that step and everything after it again, even if it succeeded. The dialog tells you how many steps run again and how many are reused.
- Cancel run asks the unfinished steps to stop. It can take a moment before the run shows Cancelled.
- Reprocess, on a recording, starts a new run from the first step. Earlier results are kept.