The run lifecycle
What each run status means and how a run moves between them, from cloning and pending through running, done, published, and archived.
Every run carries a status that tells you exactly where it is. The dashboard shows it as a badge on each use case card, and it updates in real time. This page explains each state and the transitions between them.
The states at a glance
A finished run can also be run again, for example after the definition changes, which takes it back through running to a fresh done.
What each state means
| State | What it means | What you can do |
|---|---|---|
| cloning | Neuralift is copying the definition (and optionally the data) from an existing use case. See Cloning. | Wait a moment; the use case moves to pending automatically when the copy completes. |
| pending | The use case exists but segmentation hasn’t started yet. | Work with Neuralift on the definition and data preparation. |
| running | Segmentation is in progress. | Watch progress from the dashboard; you don’t need to keep the page open. |
| failed | The run hit an error. | Nothing; Neuralift investigates and re-runs it. |
| done | Segmentation finished and results are ready for private review. | Admins review the segment landscape and actions before anything is shared. |
| published | Results are visible to every member of the organization. | Explore segments, export, and deliver results. |
| archived | The use case is retired and no longer appears on the dashboard. Its data is retained. | Contact Neuralift if you need it back. See Archiving & deleting. |
Who moves runs between states
Neuralift manages every transition, working with your organization’s admins at each step: creating and cloning use cases, starting and re-running runs, publishing, unpublishing, and archiving. The full breakdown is in Roles & permissions.
Note. Your organization sees a run’s results only once it’s published. In every other state, including done, the results are visible only to Neuralift, who reviews them with you before sharing; admins can still see the use case itself and its inputs throughout. See Publishing.