Automatic (connectivity-triggered) retries a single path gets before it is
left to the monitor banner and a manual Retry.
Mirrors MAX_CONSECUTIVE_REFINEMENT_FAILURES in progressive/refinement.ts,
for the same reason: without a cap, a path that fails for a reason
connectivity cannot fix is re-fetched on every online transition forever. A
permanently-404 chunk classifies as Network, so the kind filter alone does
not bound it. autoRetryCount starts at 0 and is charged only by
markAutoRetryAttempt on each connectivity-triggered attempt, so this allows
exactly this many automatic attempts regardless of how many times ordinary
update sweeps or manual retries recorded the same failure. Anonymous deferred
LOD groups also use this count for archive-fault cooldown retries. Success
clears their per-episode budget, while connectivity restoration and
Retry-all explicitly reset exhausted budgets.
Automatic (connectivity-triggered) retries a single path gets before it is left to the monitor banner and a manual Retry.
Mirrors
MAX_CONSECUTIVE_REFINEMENT_FAILURESinprogressive/refinement.ts, for the same reason: without a cap, a path that fails for a reason connectivity cannot fix is re-fetched on everyonlinetransition forever. A permanently-404 chunk classifies asNetwork, so the kind filter alone does not bound it.autoRetryCountstarts at 0 and is charged only bymarkAutoRetryAttempton each connectivity-triggered attempt, so this allows exactly this many automatic attempts regardless of how many times ordinary update sweeps or manual retries recorded the same failure. Anonymous deferred LOD groups also use this count for archive-fault cooldown retries. Success clears their per-episode budget, while connectivity restoration and Retry-all explicitly reset exhausted budgets.