Evidence record / openhands
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-24-openhands-failed-automation-sandbox-starts-get-cleanup-and-bounded-retries
Failed automation sandbox starts get cleanup and bounded retries. Before propagating an unusable-start failure, the Cloud backend attempts to delete the never-used sandbox. The dispatcher classifies and retries provisioning errors within its configured attempt budget; safe status classes replace raw runtime detail in run status. Cleanup is best effort.
Channel: tagged-release. Half: both. Date: 2026-10-20 (automation 1.23.1).
Operator consequence: Check failed-run cleanup and retry records before manually deleting every failed start. Retrying before automation code ran can remove routine intervention without duplicating its work. This is separate from quota skips, and released source does not establish hosted rollout or successful deletion.
Receipt
Finding metadata
Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0
Finding ID: 2026-10-24-openhands-failed-automation-sandbox-starts-get-cleanup-and-bounded-retries
Profile citations
- OpenHands / claim / failed-sandbox-cleanup-retry
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-24-openhands-failed-automation-sandbox-starts-get-cleanup-and-bounded-retriesgithub.com/OpenHands/automation/commit/567bdbdf3bef1e0866563786d109f986b979a912tagged commit file2026-10-24-openhands-failed-automation-sandbox-starts-get-cleanup-and-bounded-retriesOpenHands/automation / openhands/automation/backends/cloud.pytagged commit file2026-10-24-openhands-failed-automation-sandbox-starts-get-cleanup-and-bounded-retriesOpenHands/automation / openhands/automation/dispatcher.py
Versioned source: run artifact