Runs, Status, and Phases
Understand the run detail page: status labels, research phases, quick actions, and why a needs-input notification is often a normal part of progress.
What the main statuses mean
- Queued: dispatch succeeded and the run is waiting for execution capacity.
- Running: work is actively progressing through the phase pipeline.
- Needs input: the run is paused until a human chooses an option, answers questions, or adds context notes.
- Failed: the run stopped on an error or blocking condition and needs explicit continuation or rerouting.
- Completed: the draft outputs are ready for review, publication, packaging, or feedback reruns.
- Canceled: execution was explicitly stopped before normal completion.
omegaXiv can pause at a normal checkpoint because the system needs user judgment, not because the run broke.
Typical examples include selecting which hypothesis to pursue, choosing a target phase for continuation, or confirming context before the next phase begins.
How the phase pipeline is presented
The run detail page exposes a phase progression strip rather than hiding execution behind a single spinner. The current UI names phases such as Problem Intake, Evidence Gathering, Research Distillation, Literature Review, Research Plan, Plan Checkpoint, Mathematical Method, Experiment Design, Validation, Insights Refinement, Paper Draft, Revision, Review Pass, and Packaging Release.
Each phase summary explains what the system is doing and what kind of outputs should emerge next. The phase history is also where you anchor continuation decisions when the run asks for input or requires a retry.
Problem Intake
Evidence Gathering
Research Distillation
Literature Review
Research Plan
Plan Checkpoint
Mathematical Method
Experiment Design
Validation
Insights Refinement
Paper Draft
Revision
Review Pass
Packaging ReleaseThese labels are the user-facing phase names shown in run detail.
When to use Quick Actions
Quick Actions are shortcuts for steering a paused or completed run without reopening the entire context form. Depending on status and permissions, the page can expose actions such as Pause run, Rerun from start, Run from last checkpoint, Rerun with feedback, Continue from selected phase, Mark completed, Publish paper, Refresh paper, Export package, Package run, and Publication workspace.
Treat these as lifecycle controls, not casual buttons. For example, a rerun from start creates a fresh child run from Problem Intake, while a rerun with feedback carries forward reviews, discussion, and annotation notes.
- ✓Use Continue from selected phase after selecting the exact phase you want to resume or reroute into in Research Progression.
- ✓The selectable window is intentionally limited to completed earlier phases, the current phase, and the immediate next phase to avoid skipping the logical middle of the pipeline.
- ✓Use Rerun with feedback when the paper already has review or annotation context worth preserving.
- ✓Use Package run only after the research outputs are stable enough to expose as a reusable release.