Workflow run issues
Fix a run that stalled, ran in the wrong place, or left output you cannot find.
Workflows are personal: the definitions you save are yours, and there is no shared organization surface for them yet. Runs happen in a workspace, so a run you started is visible wherever that workspace is.
Read the run's state first#
Open the workspace and check the Execution panel header.
| State | What to do |
|---|---|
| Running | Nothing. Open the step's session to see what it is doing. |
| Waiting on approval | A step is holding the run. Approve it, or Fail & redo it. |
| Paused | Press Resume. Nothing advances until you do. |
| Failed | The step that failed is marked on the graph. Use Fail & redo on it. |
The panel says there is no run here#
The Execution panel only shows a run that belongs to that workspace. Start a workflow from the Workflows page and Proliferate opens the workspace its run lives in. Selecting a row under Executions on the Workflows page opens the same workspace.
The run is unavailable, or stuck loading#
The runtime has not returned the run yet — usually because it is still starting up. The panel keeps polling and catches up on its own.
A step will not advance#
Agent steps finish on their own. Two things hold one open:
- The step has Requires human approval set, so it waits after finishing.
- The agent is still working. Open its session and read the transcript.
If the agent went the wrong way, Fail & redo the step with a corrected prompt rather than fighting it in chat.
An action was rejected#
If the run moved before your click landed, Proliferate says the run already moved on instead of applying the action. The panel is up to date at that point; look at the graph and act again.
For anything else, the action may or may not have been applied — the panel keeps following the run either way, so wait a moment before retrying.
You cannot find what a run produced#
Context documents are files in the workspace under
.proliferate/context/<run-id>/, listed under Documents in the panel. The
folder is excluded from git, so documents never appear in a diff.
Everything else a step did is in the workspace itself: branch, commits, and
uncommitted changes. Open the step's session — it is titled with the step's
chain position, like 03 Implement — to see the work in context.
A run placed in a new worktree works on its own branch and cannot see another run's uncommitted changes. A run placed at repo root works in the existing checkout.
A workflow will not save#
Save needs a title, a title and prompt on every step, one path covering every step, and a connection from Inputs to the first step. Whatever is blocking it is marked on the card that caused it, or in a banner for the title and the JSON view.
Workflows listed under Legacy were saved before the rebuild. They cannot be opened or run — rebuild the ones you still want, then delete the rest.
Restarting lost a run#
It did not. Paused runs survive a restart, and a popover lists them so you can resume. If resuming fails, the run stays paused and stays in the list.