{"version":"2.1.250","anchor":"which-stall-backoff-tier-is-used-depends-on-the-lease-mode-f","canonical_anchor":"which-stall-backoff-tier-is-used-depends-on-the-lease-mode-f","heading":"Which stall backoff tier is used depends on the lease-mode flag","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/which-stall-backoff-tier-is-used-depends-on-the-lease-mode-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Which stall backoff tier is used depends on the lease-mode flag\n\nRepeat stalls take the long 2-4 minute retry tier because lease mode is off in a stock build.\n\n**What**\n\nThe reconnect delay picker now has two tiers. The long one, 120 to 240 seconds, is used on the second and later attempts of a stall run when the close was Cloudflare-mitigated, lease mode is off, there is no lease, or the lease will not outlive the next attempt. Lease mode is `tengu_slate_lantern_ember` with fallback false, so without a remote value every repeat stall takes the long tier.\n\n**Details**\n\n- Short tier remains 30 to 60 seconds.\n- The timing table is a plain in-bundle constant, never reassigned, so the numbers are not server-tunable.\n\n**Evidence**\n\n`longStallMaxMs: 240000,`\n\n- Flag `tengu_slate_lantern_ember`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.250; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Artifacts\n- Names: `tengu_slate_lantern_ember`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}