[AskeU]

Summary

A run left unfinished (a script stopped half way, a protocol loaded or paused in the Opentrons
App) keeps the robot from creating another; setup() failed with the server's bare 409.

 RunInfo(id, status)
+  current: Optional[bool]       # from the run listing
+  created_at: Optional[str]
+  finished -> bool              # stopped, failed or succeeded

 OT2
+  get_run(run_id)
+  get_unfinished_run() -> Optional[RunInfo]
+  stop_run(run_id, timeout=None) -> RunInfo
+    read the run; finished -> leave it
+    stop it; wait until finished, else TimeoutError
   setup()
     get_health, get_mounted_pipettes
+    get_unfinished_run -> RuntimeError naming it
     create_run ...
   home()
-    requires a run
+    requires a connection    # homing is a robot endpoint, not a run command

Evidence

• Before: setup() beside an unfinished run: HTTPError 409. Stopping it meant
  ot2._api.stop_run and polling ot2._api.get_run.
  After: setup() raises RuntimeError: The OT-2 holds an unfinished run <id> (idle, created ...), before creating anything; stop_run stops it and waits; home() after it works without
  a run. 9 new tests; 525 passed.
• Run on an OT-2: a run left open by a setup never stopped; setup() refused beside it, naming
  it; stop_run stopped it and a new run was set up. And a script stopped half way, its run
  stopped, the robot homed, a new run set up.

Merge Danger

Door: two-way

Blast Radius: small

setup() sends one more request (GET /runs) and refuses earlier, with a clearer message, where
it already failed. home() now works on a connection alone, where it raised before.

🤖 Generated with Claude Code

[rickwierenga]

thanks!