Bug when editing queued message: "Error submitting message App-server queued follow-up no longer exists"

[azhangd]

Environment

• Surface: macOS Desktop App
• Codex version: 26.909.11814
• OS and IDE/browser, if relevant: macOS Tahoe 26.5.1
• Model and plan or API-key authentication: ChatGPT Pro

Bug

Editing a queued message and resending it while a previous turn is ongoing causes error:

“Error submitting message App-server queued follow-up no longer exists”

Attempting to resend/changing the message results in the same error until leaving the project chat and returning to it.

Reproduction

1. Send a message in Codex chat
2. While previous turn is ongoing, queue another message.
3. Edit queued message (up-arrow) and resend.

Diagnostics

Exact error, relevant logs, or screenshot:

When it happened (with timezone) and how often:

Repeatable

[EricGT]

Welcome to the forum!

You posted this in the appropriate place on the forum for discussing and documenting a Codex bug. The forum, however, is not the official issue tracker. If the problem needs to be formally reported and tracked by the Codex maintainers, the official place is the OpenAI Codex GitHub issue tracker.

Thanks for following the posting requirements for the Codex Bugs subcategory:

Read this before you post in the Codex Bugs category

Report reproducible bugs in the Codex CLI, IDE extension, app, or web experience. Include your Codex version, environment, steps to reproduce, and expected versus actual behavior. Provide a minimal reproducible example where possible. Model hallucinations or differences in generated output alone are not considered bugs for this category. Keep each topic focused on one bug. Use the main Codex category for discussions and Feature Requests for proposed improvements. When a fix is available, con…

I asked ChatGPT to search for the closest related issue, and it identified:

App-server queued follow-up no longer exists

If that issue describes the same problem you are experiencing, consider adding a reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.

If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.