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
Preview / picker for
stakeAlert.colorMarket 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
Use this when a rule is team/event-specific.
Auto modes derive the final ID from event home/away + selection text.
Manual mode: paste exact OM selection ID.
Side-aware tip: for
Match Result + BTTS, choose Auto: Match Result + BTTS. The Worker will map Brazil as home in Brazil v Japan to W2-1, but as away in Japan v Brazil to W2-2. For a broad rule, use a market-specific pattern and a careful selection regex such as re:.*\b(?:yes|no)\b.*.Test sample
Use real event and selection text here. Patterns can be broad or regex; sample fields prove what the Worker will actually derive.
Use real event and selection text here. Patterns can be broad or regex; sample fields prove what the Worker will actually derive.
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
Admin-managed Reader settings: users only see token + enable switch. Worker URL, refresh interval, and batch size are sent by this policy after version check.
Database maintenance
Dry-run first, then clean old diagnostics or compact old stats JSON. Each option has an info button with exact impact.
Safe default: use Dry run first. These actions do not touch odds logic, mappings, settings, or player stats numeric values. They only clean diagnostics/logs or remove old raw JSON from player stats rows.
Audit log
Recent admin changes. Use this to understand who changed settings or overrides.