GUIDES · BETSLIP DOCTOR
Why can a Tail record be visible but refuse to open after my session or access changes?
A displayed result and permission to open its destination are separate. Tail binds public-result reads to the current account owner and session generation, then checks the current query observation and access state again when the record is opened. A previous screen or cached public result is not permission to reopen protected content after that state changes.
For BSD readers whose Tail record stops opening after their session or access changes · Updated
The tap uses current session and access state
Tail result queries are keyed to the current owner and session generation. Before navigation, the hook checks that the current session still matches the query observation and that the observation has not been denied or replaced. A tap can therefore be refused even when the screen previously showed a result.
The check prevents an older observation from authorizing a new navigation. A public result summary and access to a full post or report are not the same thing.
- Treat the current open result as authoritative for navigation.
- Do not use a previously painted result as a way around a current denial.
- Do not infer the cause of a specific account or session change from the tap alone.
A session change does not restore hidden content
Some public result data can be cached separately from pick details, but the guest cache contains only strict public result DTOs. It is not a saved copy of hidden picks or a private Grade report. Changing accounts or relying on old session data cannot grant that content.
If a record no longer opens, keep the protected content unavailable rather than clearing history, bypassing denial or trying another account. The visible summary does not explain why that particular access state changed.
Illustrative example: the session changes before a tap
Imagine a fictional reader has a Tail profile open, then the session owner or generation changes before they tap its report. The old result may have been visible, but the current admission check no longer matches that observation, so navigation can be refused. The reader does not switch accounts or try to recover protected content from cache. No specific account cause is assumed.
Related questions
Does a visible result guarantee that the report can still open?
No. Opening is rechecked against the current session and access state. A visible result from an earlier observation does not guarantee current permission.
Should I switch accounts to make the report open?
No. Do not use account switching or stale content to bypass a current access denial. The reason for a specific refusal cannot be inferred from the old result alone.