Stop a run after an interruption
An SDK timeout stops the client from waiting; it doesn’t stop the work on Baseten. If your script or machine stops before cleanup, deactivate the run before retrying. Use therun_id saved by your script. If you only have a session_id, find the run first.
Set your API key and run ID:
- Baseten CLI
- REST API
Use the Baseten CLI to deactivate the run. Then check the run’s status:
--yes skips the confirmation prompt:INACTIVE. If the run never created a sampler, sampler is null.
Find a run from its session ID
The training client can time out before returning a run ID. If your script saved asession_id, list your runs and find the matching session.
- Baseten CLI
- REST API
List your runs and filter by the saved session ID. Replace
YOUR_SESSION_ID with that value. --all includes inactive runs:id as RUN_ID in the deactivation command. If its status is already INACTIVE, it doesn’t need deactivation.