Refresh & Reconciliation¶
The backend periodically reads player and match state from the selected provider. Not all observations are immediately complete.
Why values can be delayed¶
Providers may return incomplete match history, delayed LP changes or rate-limited responses. The backend maintains LP observation states and queues reconciliation work when a result cannot yet be resolved.
Match LP deltas can be resolved, pending or unknown. Do not treat pending or unknown deltas as confirmed results.
Simplified flow¶
- Refresh current player and ranked/match information.
- Compare provider observations with the event participant's saved state.
- Persist reliable values and queue unresolved work.
- Retry reconciliation according to the backend's scheduling rules.
- Recalculate cached leaderboard data and notify connected clients.
Useful code entry points include backend/src/services/lp-observation-resolver.ts, lp-reconciliation.service.ts and backend/src/db/lp-reconciliation.ts.
For investigation, prefer Diagnostics CLI over manual updates to database tables.