Unclear whether a message was sent

#Symptoms

A message has an unverified result, corresponding to unverified. You do not yet know whether Telegram received it. This does not confirm that sending failed, nor does it prove the recipient read it.

You may have seen the message on Telegram while the app has not received confirmation. Conversely, a bubble appearing in the app is not enough to conclude that the message was sent.

#Common causes

The connection may drop after Telegram performs the action but before the worker reports the result. If the app resends immediately, the recipient may receive another message.

Another case is Telegram reporting RANDOM_ID_DUPLICATE: the send attempt's ID already exists. The app treats this as a reason to reconcile history, not as an ordinary error that prompts you to resend.

When the result is unclear, the app requests recent history to find a matching message. The incoming-message mechanism can also match a Telegram message to a pending bubble rather than keeping two separate copies.

#How to fix

1. Leave the unverified message as it is.
2. Check that the machine and proxy are working.
3. Open the correct conversation in Inbox.
4. Compare the sending account, content, attachments, and time.
5. Wait for synchronization or a late receipt.
6. If there is not enough evidence, assign a person to decide the next step.
7. Record the decision before creating a new send attempt.

The late-receipt path has a 24-hour window from when the job becomes unverified. A valid receipt must also meet conditions for session ownership and the relevant execution. Not every late notification is accepted.

Within that window, a valid receipt can promote the job to success. Promotion happens only once. The result ledger keeps a record of the unverified result and late receipt, but statistics do not count them as two successful sends.

The window ending does not mean the message automatically fails, is deleted, or is resent. An operator needs to check and decide.

#If it still fails

Save the local message ID, job ID, account ID, conversation ID, and the incident's time range. If a Telegram message ID is available, record it for comparison. Do not send only a screenshot of a bubble without identifying the account that performed the action.

If an agent is handling the issue, ask it to stop steps that depend on “successfully sent,” then hand the information to a person. The agent must not infer success or use redrive for an unverified job.

See Jobs and states and Dangerous actions. You can monitor through operation status, MCP operations_get, instead of making more message-creation requests.