Skip to main content
A runbook has three states you can act on: a draft you can still edit, an accepted plan waiting to run or already running, and a terminal result. Accepting is the boundary that stops accepting edits.
Run statesaccepted is the boundarydraftedit freelyacceptedplan and basis lockexecutingruns server-sideResultcompleted, failed, or canceledLocked: no edits to the plan, the goal, the models, or the GPU.cancel, revise, review, acceptIf progress stops, the run parksBlockedWaiting for an explicit recovery action from you.expires at 24hRecoverable failureA recovery path already ran and did not succeed.expires at 6hRecovery activity resets the clock. An expired run is labelled Run expired, never a fresh failure,and a run that expires without producing a billable result costs nothing.
Run statesaccepted is the boundarydraftedit freelyacceptedplan and basis lockexecutingruns server-sideResultcompleted, failed, or canceledLocked: no edits to the plan, the goal, the models, or the GPU.cancel, revise, review, acceptIf progress stops, the run parksBlockedWaiting for an explicit recovery action from you.expires at 24hRecoverable failureA recovery path already ran and did not succeed.expires at 6hRecovery activity resets the clock. An expired run is labelled Run expired, never a fresh failure,and a run that expires without producing a billable result costs nothing.

​
What the lock covers

Once you accept a runbook, its plan and its execution basis are locked. Two kinds of edit are refused while the lock holds:
  • Revising the runbook itself, meaning the phases and the execution graph.
  • Changing the optimization goal, the models, or the GPU.
Both refusals are explicit: they tell you the plan was not changed and which state the runbook is in. Nothing is silently applied and nothing is silently dropped. A request to change the goal that arrives while the lock holds leaves the run on exactly the basis you reviewed.

​
Changing an accepted plan

The remedy is the same in both states, and it is the designed route rather than a workaround:
1

Cancel

Cancel the accepted or executing runbook. Cancelling releases the whole hold.
2

Revise

Change the goal, models, GPU, or plan.
3

Review

Read the replacement and its new quote.
4

Accept

The replacement is quoted and consented to on its own terms, so the run that follows is bound to the plan you actually approved.

​
An accepted run is durable

The run executes server-side, so your browser is a viewer rather than the thing keeping it alive.
  • Closing the tab does not stop it. Re-opening the session mid-execution re-attaches to the running execution in about a second, and phases, live cost, and the Stop control resume updating.
  • An interruption never strands it. A timeout, a crash, or an interruption on our side converges the execution to a blocked, retryable state carrying resume and restart actions, instead of a run that appears to run forever.
  • Stop actually stops. Cancel aborts the underlying GPU work and finalizes the run’s billing. A cancelled run can never promote a version afterwards, and work measured before the cancel stays visible as measured results.
  • A lost feed says so. If only your view loses its live connection, the cost chip reads Reconnecting or Unavailable rather than a false $0.00. That means this view lost the feed, not that the run stopped.

​
Parked runs expire

A run that stops making progress is parked rather than deleted, so you keep the option to recover it. Parking is not permanent: a parked run that sees no activity within its window is closed out. Recovery activity resets the clock. Claiming or finalizing a recovery attempt counts as activity, and an attempt already in flight when the window elapses is protected rather than cut off. An expired run is labelled Run expired. It is not relabelled as a fresh failure and it does not present recovery buttons that would no longer work. It carries its own reason, naming the window and what it was waiting on, for example expired after 24 hours without a heartbeat or recovery action, and states that starting a new run is the way forward.

​
What a parked run costs

Parking creates no advance charge. The run’s durable usage record stays available so a recovery can resume the same execution without starting or billing it twice. When the run expires, RunInfra finalizes the recorded outcome. A run that expires without producing a billable result costs nothing.

How optimization works

What the agent measures, and how a winner is chosen.

Quality gates

Why a completed run may still decline to promote a candidate.

Pricing and credits

Quote, hold, and settlement in full.