Skip to main content
The Runs page shows all pipeline execution runs across your organization. You can also view runs for a specific pipe from the pipe’s detail page.
Runs list showing pipeline executions with status and timestamps

Filtering runs

Use the status filters to narrow the list:
  • All: show all runs
  • Queued: waiting to start
  • Running: currently executing
  • Completed: finished successfully
  • Failed: encountered an error
  • Review: paused for human review
  • Cancelled: manually cancelled
  • Awaiting Children: waiting for child runs from document chunking to complete

Run detail

Click a run to view its execution details. The run detail page shows:

Step timeline

A visual timeline of each pipeline step and its status. Steps are shown in execution order with timestamps.
Run detail showing step timeline with status indicators

Step data

Click a step in the timeline to inspect:
  • Input: data received from the previous step
  • Output: data produced by this step
  • Errors: error details if the step failed
  • Timing: start time, end time, and duration

Callback history

If the pipeline includes a callback output node, the run detail page shows a Callback History panel. This displays each callback attempt with:
  • URL — the webhook endpoint that was called
  • Status code — the HTTP response status
  • Success/Failure — whether the callback was delivered successfully
  • Attempt number — callbacks are retried on failure

Run actions

  • Cancel: stop a running or queued run
  • Link to pipe: navigate to the parent pipe
  • Link to file: navigate to the source file

Pipeline timer

When viewing a run in the pipeline editor, a timer badge appears in the top-right corner of the canvas:
  • Running: a blue badge shows elapsed time, updating in real time
  • In review: an amber badge indicates the run is paused for human review
  • Completed: a green badge shows the total processing time
  • Failed: a red badge shows the time elapsed before the failure

Real-time updates

Run status and step progress update in real time via SignalR. You see changes as they happen without refreshing the page.