Any viewer deciding whether source-backed data or an action is safe.
All modes/phases; source state is distinct from process liveness.
HELP TOPIC // league
/data-state-and-freshness · corpus 0.1 · verified 43c1c50
Data state and freshness
Read LIVE, CACHED, STALE, DEGRADED, OFFLINE, UNAVAILABLE, and AWAITING RELEASE without treating unknown as zero.
Sources
Who can use this answer.
Read the current gate
The owning surface's source status and last-success projection.
The label carries the consequence.
Loading, live, cached, stale, degraded, offline, awaiting-release, unavailable, failed, not-applicable.
Use the runtime clock
Freshness windows and source timestamps are runtime values.
Keep the right audience
Health/help projections are PII-free.
Take the next safe step.
- →
Read state next to the value.
- →
Check source and last-success age.
- →
Continue only when remaining capability is explicitly usable.
- →
Retry/wait through the bounded recovery action.
Know what changes.
What happens
Cached/stale can be useful but are not live; unavailable cannot authorize a fabricated fact.
What can be undone
Reading a snapshot is reversible; refresh and game mutations have separate semantics.
What you should see
The page says why, remaining capability, and next action.
Keep context. Do not replay blindly.
Failed refresh retains last-good data and never replaces unknown with zero.
Use local retry/manual refresh and escalate persistent source failure.
One concrete read.
Example: A cached pool with enough capacity can remain labeled usable; unavailable cannot be a zero-player list.
Runtime source: Provider/relay status, cache timestamps, processors, route loaders.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.