{"version":"2.1.269","anchor":"update-signature-check-distinguishes-a-suspended-process-int","canonical_anchor":"update-signature-check-distinguishes-a-suspended-process-int","heading":"Update-signature check distinguishes a suspended-process interruption from a real timeout","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/update-signature-check-distinguishes-a-suspended-process-int","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Update-signature check distinguishes a suspended-process interruption from a real timeout\n\nUpdate checks now distinguish a suspended process from a real network timeout\n\n**What**\n\nWhen Claude Code fetches the signature file used to verify an update package, a network failure during that request used to always be treated as a generic connection or timeout error. Now, if the elapsed time suggests the process was suspended mid-request (for example, a laptop going to sleep) rather than the network actually failing, it's reported as a distinct `sidecar_fetch_interrupted` case.\n\n**Why**\n\nThis new case is treated leniently and simply retried on the next check, rather than being escalated as a real error, so a laptop sleeping mid-update-check no longer looks like a failed update.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}