Sports distribution
Unique processed bets, not sporting events.
Operations & performance
Read-only Expected Margin processing health, benchmark attribution, timing, failure and reconciliation signals. All range grouping is UTC.
Not loaded
Connect to load operational data.
Processing status
All eligible processing runs in the selected range.
IP / PM activity trend
UTC buckets; successful, partial, failed, skipped and pending runs.
Benchmark sources
Requested attempts, response-reported source and selected usable benchmark are separate.
Failure & attention
Actionable categories. Click to open the appropriate Admin view.
Top reason codes
Click a reason to filter the detailed list below.
Detailed attention list
Latest matching processing runs, capped at 100.
IP timing
Normal display window, IPd conversion, timing expiry and recorded latency.
PM benchmark path
Price-only PM source successes, archive use and lifecycle.
Data quality & reconciliation
Actionable counts linked to Inspector, Reconciliation, Mappings or Diagnostics.
Metric definitions and denominators
Processing pipeline
Shadow-only observability. The ledger records what the existing production flow did; it does not control pricing, source selection, result calculation, or badge writing.
Coverage: funnel counts start after HF1164 deployment. Older bets remain available in BT Inspector through a read-only fallback to existing production tables.
Load the funnel after deploying the HF1164 migration and Worker.
Incomplete / warning reasons
Benchmark sources
Reconciliation dry run
Read-only detection of incomplete or stale flows. It never recalculates, rewrites, retries, or changes production rows.
Use the Pipeline filters above, then load the dry run.
BT Inspector
Enter a parent BT ID, internal bet ID, PTL ID, or raw bet ID to see the end-to-end processing evidence, selected bookmaker ID, attempted sources, and recheck feed consistency.
No bet inspected yet.
Runtime Policies
Versioned operational rules stored in D1 and cached per Worker isolate for exactly five minutes. Safe compiled defaults remain football-only.
Propagation: publishing does not redeploy code. Warm isolates refresh within 300 seconds; cold isolates load the active policy immediately. Drafts never affect production.
Load Runtime Policies to begin.
Version history
Published, draft, archived, and rollback-clone versions.
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
Leave empty for future similar events. Use only when the rule is truly team/event-specific.
Auto modes derive the final ID from event side, yes/no, over/under, or first N+ number.
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 see only Reader enable, token, late-alert enable, and their alert ticker link. 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.
Cloudflare diagnostics
Read-only production checks for bindings, secret presence, D1 schema profiles, request limits, and fallback warnings. Secret values are never returned.
Interpretation: red means a required item is missing; yellow means production can run but may use a less reliable fallback. This page does not change Cloudflare configuration.
Diagnostics not run yet.
Audit log
Recent admin changes. Use this to understand who changed settings or overrides.