Repeat stalls take the long 2-4 minute retry tier because lease mode is off in a stock build.
A lease-aware short-retry tier exists but lease mode (tengu_slate_lantern_ember) falls back to off, so stock builds never use it.
tengu_slate_lantern_ember On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.250: on
Read once, for one account on one subscription tier, against v2.1.250. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The 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.
- Short tier remains 30 to 60 seconds.
- The timing table is a plain in-bundle constant, never reassigned, so the numbers are not server-tunable.
longStallMaxMs: 240000,
Strings lifted out of the shipped bundle, so the claim above can be checked against them.