{"version":"2.1.304","anchor":"timeouts-on-internal-abort-signals-are-now-capped-at-a-maxim","canonical_anchor":"timeouts-on-internal-abort-signals-are-now-capped-at-a-maxim","heading":"Very long timeouts are now capped instead of firing immediately","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/timeouts-on-internal-abort-signals-are-now-capped-at-a-maxim","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Very long timeouts are now capped instead of firing immediately\n\nClaude Code now caps how long it waits before cancelling an operation on a timeout, so a very long requested wait fires no later than a fixed maximum\n\n**What**\n\nSome operations in Claude Code are cancelled automatically if they take longer than a set time. The step that schedules that cancellation now limits the wait to a fixed maximum. Before, the requested time was used exactly as given.\n\nA very long requested timeout now fires no later than that maximum.\n\n**Why**\n\nA timer asked to wait for an extremely long time can end up firing straight away instead. Capping the wait stops an oversized timeout from cancelling an operation the moment it starts.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}