Worker settings, market mapping overrides, missing mappings, and UserReader version control.
Not connected
Dashboard
One place to check whether the Admin API is connected and how many config rows exist.
Admin safety rule: overrides affect future Worker mapping only. Old bets are not recalculated unless we build a reprocess job later.
Worker settings
These values are stored in D1 and read by the Worker runtime cache. They do not redeploy code.
Use carefully: keep archive priority as 216 unless archive Pinnacle/Bet365 entitlement is confirmed.
Edit setting
Market mapping overrides
Overrides are checked before building raw bet IDs for future rows. Lower priority number wins.
Recommended flow: create from a missing mapping, paste the correct selection ID, test draft, save. Priority 100 is normal; use 10 only for emergency/specific rules.
Override rule
No test yet.
Missing mappings
Rows the Worker could not map. Create override fixes future rows; Resolve only hides the item.
Resolve vs Create override: Resolve = close/ignore. Create override = prefill form so you can add the correct selection ID.
UserReader version control
Controls what UserReader version is current, and can block old Readers from badge/player-stat endpoints.
Force update: old/no-version UserReader requests return HTTP 426. Users must replace/reload the extension manually.
Current UserReader policy
Audit log
Recent admin changes. Use this to understand who changed settings or overrides.