GUIDES · BETSLIP DOCTOR
What should I do if submitting my appeal is interrupted?
If BSD says your appeal could not be confirmed, keep the saved appeal text and use the same Appeal decision action again as the on-screen message instructs. The app stores the appeal body and request key for that case before sending, so an unchanged retry can reuse the same request identity. Current case, decision, source and access checks still apply; a local saved draft is not proof the server received it or a promise that the appeal will succeed.
For BSD members whose free-club appeal submission was interrupted or could not be confirmed · Updated
Retry the saved appeal for the same case
The appeal form saves its body and command key locally for the specific club and case before it submits. If submission is interrupted, the card says the appeal could not be confirmed and instructs you to retry the same submission.
Keep the saved text unchanged and use that same case's Appeal decision action when it remains available. The app reuses the saved key for the matching case and body; it is not a prompt to write a second appeal.
A retry still checks the current decision and source
The server binds an appeal to the original case, decision ID, club-post target and source revision. It checks the subject role and current eligibility before accepting or replaying the command.
If the request never reached BSD, a local draft does not prove it was received. If the case or source changed, the retry may return an unavailable or stale response. The source does not guarantee eventual delivery or that every interruption can be recovered.
- Stay on the same content review and keep the original appeal text.
- Use the on-screen retry instruction rather than creating another appeal.
- If the current case no longer offers the action, do not infer a final appeal result from that alone.
The recovery action is not a new appeal opportunity
The same command key lets the backend recognize the same request when the request identity matches. A different body, case or command is not the same retry, and an appeal does not create a second right to challenge the same decision.
A confirmed submission changes the original case to Appealed and creates a linked appeal case. That is a filing status, not a decision about the appeal.
Hypothetical: connection loss during an appeal
Suppose you write an appeal for an eligible decision and the connection drops while you submit it. The case card says the appeal could not be confirmed and asks you to retry the same submission. You keep the saved text and use that same action. If BSD recognizes the matching command and current eligibility still passes, the replay can return the existing case status. If the original request never arrived or its source checks no longer pass, the saved draft alone cannot prove acceptance.
Related questions
Should I write a new appeal after an interruption?
No. Use the saved text and same-case retry instruction. The stored request identity is meant to check that submission, not to start a second appeal.
Does a saved appeal draft prove BSD received it?
No. The app saves the draft before sending. A server receipt or updated case status is needed to confirm what BSD recorded.