---
title: "A send result is waiting for confirmation"
description: "An uncertain send retains the draft while its receipt is checked."
slug: "send-pending-confirmation"
category: "troubleshooting"
language: en
editorial_status: published
capability_status: available
reviewed_at: 2026-10-13
keywords: ["CueSpec uncertain send","pending receipt","avoid duplicate AI message"]
---

# A send result is waiting for confirmation

An uncertain send retains the draft while its receipt is checked. Inspect the original Codex conversation before allowing another attempt, because the first message may already have arrived.

## 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.

## Related reading

- [A message seems to appear twice](/duplicate-message-display/)
- [Delivery receipt versus task completion](/receipt-vs-completion/)
- [Transcription takes longer than expected](/transcription-slow/)
- [CueSpec product facts at a glance](/product-facts/)