GUIDES · BETSLIP DOCTOR
Why did my Doctor question return to the text box after a send problem?
Doctor can restore a question to the composer when a send attempt does not complete, so you do not lose the text. But seeing the text again—or seeing a network error—does not by itself prove whether the server accepted a quote or started a job. Doctor checks the persisted request journal and acknowledges the exact question only when its successful job and matching saved messages are bound to the same account and chat. Wait for the existing recovery state and review the conversation before acting; avoid repeatedly pressing Send on an uncertain request. A Grade is a second opinion, not a pick.
For BSD readers whose Doctor question returned to the composer after a send problem. · Updated
A restored question is composer text, not a verdict
The send flow clears the composer while trying to start a message. If the request fails before it is acknowledged, Doctor can put the text back in the box, subject to the same account, chat and draft revision. This protects the wording; it does not tell you by itself what happened on the server.
Doctor reconciles the exact request before clearing it as sent
The app treats the message as acknowledged only when the successful job and the matching saved user and Doctor messages are bound to the intended thread. If a response is uncertain, Doctor can reload and retry the persisted command rather than create a new command from the same text.
Check the current thread before trying again
Look for the question and reply in the current conversation and follow Doctor's displayed recovery action. Do not infer that a network error means no server acceptance or no accounting, and do not blindly submit the same request repeatedly. Not every failure is guaranteed to restore text.
Hypothetical example: a lost response is uncertain
Suppose the connection drops just after you press Send and the question reappears. The text may be restored, while the saved command journal still needs to reconcile the original attempt. Check the thread and use its recovery state instead of tapping Send several times. The text box alone cannot establish whether the server accepted the request or how it was accounted for. This is a synthetic network example, not a real consultation.
Related questions
Does text returning to the composer mean the server did not receive it?
Not necessarily. A network failure can leave the outcome uncertain while Doctor reconciles the persisted command and saved messages.
Should I press Send again right away?
First review the current conversation and its recovery state. Repeated submissions can create confusion when the original request is still being reconciled.