{"version":"2.1.268","anchor":"settimeoutsetinterval-globally-proxied-to-clamp-overflow-de","canonical_anchor":"settimeoutsetinterval-globally-proxied-to-clamp-overflow-de","heading":"setTimeout\/setInterval globally proxied to clamp overflow delays","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/settimeoutsetinterval-globally-proxied-to-clamp-overflow-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### setTimeout\/setInterval globally proxied to clamp overflow delays\n\nClaude Code now clamps overly long setTimeout\/setInterval delays instead of letting them silently misbehave\n\n**What**\n\nClaude Code now wraps the global `setTimeout` and `setInterval` functions at startup so that any delay value greater than 2147483647 (Node.js's 32-bit limit for these timers) is automatically clamped down to that maximum before the timer runs. When a clamp happens, it logs a warning and, once per relevant case, records telemetry about it.\n\n**Why**\n\nWithout this, a timer scheduled with too large a delay would silently fire almost immediately instead of after the intended wait, an easy-to-miss bug; clamping it and warning makes that situation visible instead of silent.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}