{"version":"2.1.250","anchor":"load-shed-disconnects-drop-the-reused-token-lease","canonical_anchor":"load-shed-disconnects-drop-the-reused-token-lease","heading":"Load-shed disconnects drop the reused token lease","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/load-shed-disconnects-drop-the-reused-token-lease","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Load-shed disconnects drop the reused token lease\n\nOverload-related disconnects now back off and fetch a fresh token instead of reusing a stale one.\n\n**What**\n\nA disconnect classified as a load shed, meaning a Cloudflare-mitigated close or a 5xx\/429\/408 upgrade rejection, now both counts as a stall for backoff purposes and deletes the cached token lease instead of keeping it through up to three failed dials.\n\n**Details**\n\n- The shed classification is computed before the stall check in the socket lifecycle handler.\n\n**Evidence**\n\n`...(Ne && { shed: !0 }),`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}