GUIDES · BETSLIP DOCTOR
Why can a saved research report have different creation and availability times?
The saved report carries separate createdAt and availableAt timestamps. History displays Available using the availability timestamp and uses availability—not creation alone—for the advice chronology comparison and ordering. The two values can differ because they represent separate source fields, but that difference does not establish processing duration, delivery latency, or when anyone read the report.
For Bettors reading report timing in the History advice timeline · Updated
Creation and availability are separate fields
The report record contains a creation time and an availability time. The History parser validates both values and rejects a record whose availability time is earlier than its creation time.
The timeline displays Available with the availability value. It does not replace that value with the report's creation time just because creation happened earlier.
Availability is used for the timing comparison
History orders advice entries by availability time and uses the server-provided timing label to compare report availability with the ticket's recorded placement. Creation time alone does not establish that the report was available before placement.
This keeps the chronology tied to the time field used by the History record. A difference between created and available does not tell you how long processing or delivery took.
Neither timestamp proves someone read the report
An availability timestamp describes the report's recorded timeline field. It is not proof that a person opened, noticed, or read the analysis at that time.
Read the displayed field labels literally and retain the source timing. Do not infer attention, delivery latency, or a particular processing explanation from the difference between timestamps.
A report with two times
Hypothetically, a saved report's createdAt value is earlier than its availableAt value. History shows the Available time and uses it in the chronology. The interval between the values does not by itself establish processing duration or when a reader saw the report.
Related questions
Does the creation time prove the report was already available?
No. History uses the separate availableAt field for the chronology comparison.
Does the difference show delivery latency?
Not by itself. The source provides separate timestamps, but the interval is not a supported processing or delivery measurement.