The Runs page lists application packs created from flows. One row is one application being collected, processed, reviewed, or decided.

Route: /flows/runs/

Example:

https://default-company.localhost/flows/runs/

The implementation is a paginated list view. It displays up to 50 runs per page, newest first.

Filter by flow

Use the selector above the table to show:

  • All flows; or
  • runs belonging to one selected flow.

The filter is stored in the URL as ?flow=<flow-id>. Pagination preserves the selected flow.

Select Flows in the header to return to the flow list.

Columns

Column Meaning
Reference The external reference entered when the run was created. A shortened run UUID is used when it is empty.
Flow The flow definition used by this application.
Submitter The run's submitter_type profile value, when available.
Status The current run lifecycle state. Colour helps distinguish processing, warning, successful, and failed states.
Documents The number of stored files in the run.
Created The run's creation date and time.

Select a row or its reference to open Run Detail.

Run statuses

Status Meaning
Draft A run record exists but collection has not started.
Collecting documents The run is waiting for uploads or has just staged an upload.
Processing Automated classification, extraction, validation, or checking is running.
Needs review The run has been assigned the explicit review status.
Ready for decision Automated processing completed and produced a recommendation. An officer can record the final decision.
Decided An officer recorded Proceed, Send back, or Reject.
Failed The automated pipeline stopped because of a technical error. This is not an applicant rejection.

For a decided run, the badge colour also reflects the officer decision: Proceed is successful, Send back is a warning, and Reject is an error.

Empty state

When no runs match the current filter, the page asks you to open a flow and use New Run. Runs are created from the flow builder, not from the Runs list.