A stopped run can't take a backend change: let it adopt its profile's new settings and re-plan apply on resume #352
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
What we want
A stopped (or failed) run can take a change to its backend and carry on with it, without breaking #313's guarantee that a live run isn't changed under its feet. This needs design, mainly around the profile versus the run's own copy. Some shapes:
Done when
Where to look:
POST /api/runs/{id}/stopand/resume;provision()insrc/osf/agent/server.py;.osf/budget.json#groupsandBUDGET_GROUPS_FANOUTinsrc/osf/engine/executors.py, plussrc/osf/engine/estimator.py;POST /api/steps/{id}/redoandrerun-stale.Related: #324, each run's own backend state in the top bar.
Found during braid#350 run D, 2026-10-31. Requested by the owner.
Shipped in PR #421 (
ff9381d8), changeresume-adopts-profile, scoped to the second shape in the body. A stopped or failed run's detail carriesbackend_moved, the keys of its copy that differ from its profile as saved now (window, per agent, output reservation, effort, step levels, model, URL, …), and the run page shows "Resume with the backend as it is now" beside Resume (shift+R), with what moved in its hover. It rewrites the run's copy from the profile, records the adopted keys onosf.run.resumed, and the supervisor provisions the server from the new copy (a server still up from before the stop is replaced). Plain Resume keeps the copy; a live run is never changed. No re-plan step was needed: the apply fan-out decides one step or groups from the run's copy when it is reached, so a run stopped before apply gets one step on the larger window, and a run inside a split apply keeps its parts. Switching a run to another profile is not in this. Tests:tests/api/test_resume_adopt.pyand a journey.