{"version":"2.1.292","anchor":"interruptidle-handling-usage-limit-repeats-safetystops-in","canonical_anchor":"interruptidle-handling-usage-limit-repeats-safetystops-in","heading":"Interrupt requests report stale or invalid worker errors","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/interruptidle-handling-usage-limit-repeats-safetystops-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Interrupt requests report stale or invalid worker errors\n\nInterrupt requests can now fail with stale_worker_epoch or invalid_worker_epoch, and result totals now include a count of safety stops\n\n**Unclear.** What `safetyStops` counts, and when it is nonzero, is not stated.\n\n**What**\n\nThe interrupt control request asks a running session to stop. Programs that drive Claude Code use it, and it now documents two error codes for claude-code-server tenants:\n\n- `stale_worker_epoch`\n\n- `invalid_worker_epoch`\n\nThe totals reported with a held result now also include `safetyStops`. The main run loop also gained a check for repeated usage-limit alerts.\n\n**Why**\n\nPrograms that host Claude Code can tell an interrupt aimed at an out-of-date worker apart from other failures, and handle each case on its own.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}