GUIDES · BETSLIP DOCTOR
My report may have sent, but I did not get confirmation. Should I send it again?
Do not start a second report just because the connection dropped. In the same free club, use Retry report on the saved request; BSD keeps that request's original key, reason, details and expected post revision. A retry can recover the same submission when the current source and access checks still pass, but no confirmation does not prove the server received an offline request.
For BSD members who submitted a free-club post report but did not receive confirmation · Updated
A missing confirmation leaves the result unknown
A connection can fail after you start sending a report and before the app receives a receipt. That does not tell you whether BSD accepted the report. Look for the saved report in the same free club rather than filing a new complaint immediately.
If the app shows the item in Reports to finish, or shows Retry report for that post, use that saved item. If an accepted receipt and case reference already appear under Your content review, check that case's status instead of retrying a new report.
Retry the unchanged saved request
Retry report reuses the saved command key, reason, optional details and expected revision for the same club post. It is the recovery action for that saved submission; it does not create a new complaint with a new request key.
BSD's replay check can return the existing case status when it recognizes the same actor, command and request and the current source checks still pass. That check is not a universal exactly-once guarantee. If the original request never reached BSD, there may be no server receipt to recover.
- Stay in the same free club and use Retry report on the saved item.
- Do not change the reason or details to turn the retry into a different report.
- If the post changed or current access cannot be confirmed, follow the app's message and do not assume a report was accepted.
Use a receipt or case status to confirm what BSD recorded
An accepted receipt has a case reference and pending status. Until you see that receipt or a saved case status, the local retry record only shows that the app kept a request to finish; it does not establish that BSD received it.
If the saved request cannot be retried or its status cannot be checked, keep any case reference you already have and use BSD's published support contact. Do not submit repeated new reports to test the connection.
Hypothetical: the connection drops during a report
Suppose you choose Send report for a post in a free club, then your connection drops before a receipt appears. When you return, the app shows the saved item under Reports to finish. You choose Retry report on that item. The app reuses the original request values; if BSD already recorded that exact command and current source checks pass, it can return the existing case status. If the source or access check fails, the retry may not complete. The missing first receipt alone does not show which happened, so do not create a separate report to find out.
Related questions
Does no confirmation mean my report was not sent?
No. It means the result is unknown from that screen. The server may or may not have received the request; use the saved Retry report action when it is available.
Will Retry report always recover the first submission?
No. The retry reuses the saved request identity, but BSD still checks the current source and access. If the original request was never received or those checks no longer pass, the retry cannot promise an accepted receipt.