GUIDES · BETSLIP DOCTOR
Why does History ask me to reload when a record or its advice history changes?
History ties an advice timeline to the saved record identity and revision read with it. If a later page or refresh no longer matches that record, generation, or advice summary, the feed drops the stale chronology and asks you to reload the saved record. This prevents older advice rows from appearing to belong to a newer record. The prompt does not by itself mean a sportsbook outcome changed or an account was compromised.
For Bettors reviewing saved Grades and their History chronology · Updated
The timeline belongs to a specific record version
An advice response carries the record identity and fields such as revision, source digest, placement time, and placement source. History checks these values when reading the advice timeline.
It also checks that later pages belong to the same generation and record context as the first page. A page or summary that no longer matches is treated as changed data, not appended to the old chronology.
Reloading avoids combining two versions
If a record or its advice history changes during a read, showing old rows beside new record details could imply a sequence the data no longer supports. History clears that stale view and asks you to reload the saved record to review its current chronology.
The prompt is a consistency safeguard. It reports a mismatch; it does not explain why the source changed or make a claim about the ticket's settlement.
- Reload the saved record to request its current chronology.
- Do not combine old advice rows with newly changed record details.
- A changed chronology is not evidence of fraud or account compromise.
Keep the conclusion narrow
A revision or generation mismatch means the current view no longer matches the exact chronology being read. It does not diagnose a particular account or show that a reported action occurred.
After reloading, review the returned record and timeline together. If the mismatch continues, the current view cannot establish one sequence from the mismatched data.
A timeline changes between pages
Hypothetically, a reader opens the first page of a saved record's advice history. Before another page loads, the record revision changes. History refuses to append the older page to the changed record and asks the reader to reload, keeping the chronology tied to one version.
Related questions
Does the reload prompt mean the ticket result changed?
No. It means the record or advice chronology no longer matches the version being read; it makes no settlement claim.
Can I treat older rows as part of the refreshed record?
Do not merge them yourself. Reload so History can read the current record and its advice timeline together.