GUIDES · BETSLIP DOCTOR
What should I do if I am unsure whether a private message was sent?
First check the current conversation and message result before sending anything again. If the send result is unknown, the recorded messaging flow uses a persistent command key: a retry with the same key and same body recovers the existing command, while a new command can create a second action. A conversation request can be pending moderation, which is not proof of delivery. Use only a retry the current client supports, and do not treat uncertainty as confirmation that the message was sent or not sent.
For BSD community members unsure whether a private message was sent · Updated
Look at the current conversation first
Before composing again, check the intended thread and its current messages or result if your client exposes them. A delayed response can leave the sender unsure even though the original request is still being reconciled.
Do not start a new message with different content or a new request identity until you have checked whether the original action appears.
Use the same request for a supported retry
The canonical messaging operation persists commands by command key and replays the same request when the key and body match. That makes an exact retry different from composing a new command that could create a duplicate.
If your current client offers a retry, use that flow rather than changing the message or generating a fresh send. The backend source does not establish a universal retry button or screen.
A pending request is not proof of delivery
A conversation request may be pending moderation. Its receipt describes that pending state and is not confirmation that a recipient received or read a message.
Use the current thread/result state to understand what happened. Do not interpret a timeout, pending state, or missing read status as proof either way.
Hypothetical: the send result is unclear
Imagine a member submits a message and the client does not clearly show the result. The member checks the intended conversation before acting again. If the current client provides a retry, it reuses the same request rather than creating a second message with a new command. A pending request remains pending; the example does not claim delivery.
Related questions
Should I send the same text again with a new request?
Not before checking the current thread. A new request can create a duplicate; use the current client's supported retry for the original request if available.
Does a pending conversation request mean the recipient received it?
No. The recorded request receipt can be moderation-pending and is not proof of delivery or reading.