GUIDES · BETSLIP DOCTOR
What should I check if a saved record seems missing after changing BSD accounts?
First confirm which BSD account is currently signed in. History reads are authorized for that current account, so a record associated with a different account may not appear when you switch identities. Then identify whether the expected entry was an imported sportsbook record or a manual record. An absent row in one account does not prove the source record was deleted or that you should request access to someone else's history.
For BSD members reviewing a record after signing into a different BSD account · Updated
Confirm the account that is signed in now
An account change changes the identity used for the current History request. Before looking for a record, confirm that the BSD account you intended to use is the one currently active. A device or app session is not itself proof that two BSD accounts share the same saved records.
If you cannot verify the account safely, use BSD's normal sign-in and support paths. Do not share passwords, sign-in codes, session data or another person's account access to troubleshoot a missing row.
- Check the current BSD identity before interpreting an empty or partial History result.
- Recall which account was active when the record was saved or imported.
- Keep another person's account and records out of the check.
Identify the kind of record you expected
BSD represents sportsbook imports and manual records as different record types. Their source and result labels answer different questions. An imported entry reflects the record available from its import source; a manual entry is recorded from information supplied by the member. A source label does not by itself reveal which BSD account you used at another time.
Use the record you remember and the current account's own authorized History data to narrow the question. Avoid assuming that an import is present in every signed-in account or that a record was manually created just because it is absent from the current view.
Keep the review limited to the record you need
If the correct account is active and the entry still cannot be found, keep the missing source, record type and approximate date as the unresolved facts. A current account's available History read is the appropriate scope for that account. The missing row is not permission to inspect an unrelated account or request a complete history export.
Do not relink a sportsbook, recreate a manual result or treat the entry as deleted solely because it did not appear after switching accounts. Those steps can change or duplicate records and are not needed to confirm which account is active. For a persistent account-scoped issue, use the public BSD Support destination without sending credentials or unrelated records.
Illustrative example: a record is absent under the currently signed-in account
Imagine a member has used two BSD accounts on one device. After switching accounts, they expect to see an imported record from an earlier session, but the current account's History read does not show it. They first confirm which BSD identity is active, then keep the expected record type and date in view. They do not ask another account holder for credentials or browse unrelated records. This fictional example does not imply that either account contains a real record.
Related questions
Does switching accounts move saved records to the new account?
The current History read is scoped to the authenticated account. Do not assume records move when the signed-in identity changes. Confirm which account owns the record through its own authorized access.
Should I reconnect my sportsbook to find the old record?
Do not reconnect or create a replacement record just because an entry is absent after switching BSD accounts. First confirm the current BSD identity and whether the expected entry was an import or manual record.
Should I send BSD my password or another account's history?
No. Keep credentials, sign-in codes and unrelated account records private. Use BSD's public support destination for a persistent account-scoped question.