{"version":"2.1.311","anchor":"two-new-typed-api-error-kinds-for-unattended-cloud-session-r","canonical_anchor":"two-new-typed-api-error-kinds-for-unattended-cloud-session-r","heading":"Two new error types for cloud sessions that restart on their own","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/two-new-typed-api-error-kinds-for-unattended-cloud-session-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Two new error types for cloud sessions that restart on their own\n\nSDK results can now report `unattended_start_limit` and `unattended_start_unconfirmed` errors for cloud sessions restarted without anyone present\n\n**What**\n\nThe SDK lets other programs run Claude Code and read its results. Its list of API error types has two new values. Both are about cloud sessions whose process restarts with nobody watching:\n\n- `unattended_start_limit`: a restarted cloud session refuses to carry on with unfinished work. This happens once it reaches the configured number of unattended starts in 24 hours. No request is sent.\n\n- `unattended_start_unconfirmed`: Claude Code could not read or write the record of those starts. This error does not end the session.\n\nBefore this change, the list ended at `empty_completion`.\n\n**Why**\n\nPrograms that react to specific error types will now see these two values. They should know there is now a cap on how often a cloud session can resume work by itself.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}