Description
A prepare run has no pause. Once Prepare starts, the only ways to stop it are per-row cancel (one CID at a time) or closing the tab. Closing the tab is actually safe — completed pieces persist and the next Prepare recomputes only what is missing — but nothing in the UI says so, and it is a blunt way to express "stop for now, keep my progress." On a multi-hour run (a 2M-CID inventory runs for a day or more even at the current rates) an operator will reasonably want to pause for bandwidth, a meeting, or an overnight stop, and today they either kill the tab on faith or let it run.
Impact
Operators either abandon progress they didn't need to lose or avoid pausing at all. The persistence guarantees (#26, #57) already do the hard part; the control is missing.
Next steps
- A Pause control while a run is live: stop handing new CIDs to the worker pool, abort in-flight rows back to queued (not failed), flush the persisted snapshot.
- Button reads as state: Prepare → Pause → Resume; Resume is the existing incremental Prepare.
- Say in the UI that closing the tab is also safe, since that is the pause everyone reaches for first.
Done means
Mid-run, one click pauses within seconds with nothing lost; Resume (or a reload, or another device restoring the run) picks up exactly where it stopped; completed counts never go backward.
Description
A prepare run has no pause. Once Prepare starts, the only ways to stop it are per-row cancel (one CID at a time) or closing the tab. Closing the tab is actually safe — completed pieces persist and the next Prepare recomputes only what is missing — but nothing in the UI says so, and it is a blunt way to express "stop for now, keep my progress." On a multi-hour run (a 2M-CID inventory runs for a day or more even at the current rates) an operator will reasonably want to pause for bandwidth, a meeting, or an overnight stop, and today they either kill the tab on faith or let it run.
Impact
Operators either abandon progress they didn't need to lose or avoid pausing at all. The persistence guarantees (#26, #57) already do the hard part; the control is missing.
Next steps
Done means
Mid-run, one click pauses within seconds with nothing lost; Resume (or a reload, or another device restoring the run) picks up exactly where it stopped; completed counts never go backward.