Check before retrying#
Look for the exact text and attachment in the intended conversation. If it is present, follow the task’s state rather than sending again. If it is absent, use the documented confirmation flow only after establishing non-delivery.
The release describes a recovery action for a user-confirmed unsent message. It restores the ability to send; it does not immediately and automatically replay the instruction.
Distinguish the states#
No receipt yet is not the same as a definite rejection. A confirmed receipt is not the same as completed AI work. A model-busy state after delivery should not prompt a duplicate send.
Keep the useful draft and avoid changing several variables while checking receipt. For a report, note the visible send state, whether the original conversation contains the message and the app version. Remove private task content. The current behavior is intended to reduce duplicate delivery, while difficult host-version and concurrency cases still need their own verification.