GUIDES · BETSLIP DOCTOR
Can I recover a pending report if the post is no longer in my feed?
If an unconfirmed report was saved, the free-club screen can list it under Reports to finish even when that post is absent from the current feed. Choose Retry report on that saved item to resume the same request. The control does not guarantee access to a removed post or successful submission: BSD still checks the current account, club, source and revision. If you already received an accepted case reference, check Your content review instead; a post disappearing from your own feed is not a decision.
For BSD members with a pending free-club post report that is no longer visible in the feed · Updated
A saved request can appear separately from the current feed
The Reports to finish card is built from the free-club app's saved pending requests. It can show a saved report when the post is no longer among the feed items currently loaded for that club.
Open the same free club and look for the saved item. Use Retry report on that item if you want to resume that submission. The card preserves the request information; it does not restore the post or promise that the server will still accept it.
A recovery control does not bypass source or access checks
The retry uses the saved command key, reason, details and expected revision. BSD checks that the current account and club access are still valid and verifies the report's source and revision before completing the request.
If the post was deleted, changed, or is no longer available under the current source rules, or if your access changed, Retry report may not produce an accepted receipt. The presence of a saved item is not proof that the server received the first attempt or that the post can still be reported.
- Use the saved item in Reports to finish rather than starting another report for the same event.
- Follow the app's response if the source changed or access cannot be checked.
- Use the case reference under Your content review for status after an accepted receipt.
Separate an unfinished request from a received report
Reports to finish is for a saved request that has not produced an accepted receipt in the app. After BSD returns an accepted receipt, the client saves the case reference, clears that pending request and hides the post from your own free-club feed.
If the post vanished after an accepted receipt, use the saved case card to check its current status. The local feed hide does not show whether a reviewer upheld or dismissed the report, and it does not promise that the post was removed for everyone.
Hypothetical: the saved post is absent from the feed
Suppose you start reporting a free-club post, but the connection fails before the app receives a receipt. Later the post is no longer in the loaded feed, while the saved request appears under Reports to finish. You choose Retry report on that saved item. If the current account, club, post source and saved revision still pass their checks, BSD can continue the same request. If they do not, the control cannot restore access or promise acceptance. If you had already received a case reference, check that case instead of treating the missing feed item as a new result.
Related questions
Does Reports to finish mean the post is still available?
No. It means the app retained a request to finish. Retry report still depends on current source, revision and access checks.
If the post disappears after BSD accepts my report, should I use Retry report?
Use the saved case reference under Your content review to check status after an accepted receipt. A local feed hide does not mean the report needs to be submitted again.