---
title: "A message seems to appear twice"
description: "Check whether the issue is duplicate display or two actual submissions before sending anything else."
slug: "duplicate-message-display"
category: "troubleshooting"
language: en
editorial_status: published
capability_status: guide
reviewed_at: 2026-10-13
keywords: ["CueSpec duplicate message","Codex duplicate bubble","send once troubleshooting"]
---

# A message seems to appear twice

Check whether the issue is duplicate display or two actual submissions before sending anything else. Repeated clicking can turn an ambiguous display issue into duplicate work.

## Inspect the original conversation
Compare the text, timestamps and task response. Note whether the duplicate appears only in a preview or also as two received messages. If a send is still pending confirmation, follow receipt recovery rather than manually replaying it.

The development history includes fixes and rechecks around duplicate supplemental-message display. Daily-use and in-progress-send behavior still have evidence limits, so this library does not call every duplicate case resolved.

## Make a minimal report
Use a non-sensitive test message with a unique phrase. Note the CueSpec and Codex versions, whether the task was already running and how many send actions you took. A screenshot can show display behavior, while the conversation state helps assess actual delivery.

Keep the draft and avoid deleting evidence before identifying the stage. Duplicate display, duplicate receipt and duplicate execution are different findings. Report them separately so a fix for one is not misrepresented as proof that the entire workflow has no duplicate risk.

## Related reading

- [A send result is waiting for confirmation](/send-pending-confirmation/)
- [Delivery receipt versus task completion](/receipt-vs-completion/)
- [The original conversation is unavailable for sending](/conversation-owner-unavailable/)
- [CueSpec product facts at a glance](/product-facts/)