Queued follow-up message fails with “App-server queued follow-up no longer exists”

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.908.40834

What subscription do you have?

pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

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

add logs
codex-desktop-276be196-ca36-4422-bdae-1d4b5a46fdc0-46436-t0-i1-000013-0.log

What steps can reproduce the bug?

Steps to reproduce:

Start a long-running Codex task.
While the task is still running, enter and submit a follow-up message.
Wait for the current task to continue/finish. In my case, automatic context compaction also occurred during the run.
Observe the queued follow-up message.

What is the expected behavior?

Queued follow-up messages should remain associated with the current conversation and be submitted automatically after the active Codex task finishes.

The queued message should not disappear or become invalid because of context compaction, task state changes, or other internal processing.

Additional information

The issue is intermittent and does not happen every time.

I have observed it during long-running Codex tasks when a follow-up message is submitted while the current task is still running.

In some cases, context compaction or other internal task processing occurs before the queued message is handled. After that, the following error may appear:

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

I have not yet found a fully reliable way to reproduce the issue. Sometimes queued follow-up messages are processed normally, and sometimes they fail with this error.

When the issue occurs, the message remains visible in the input area and has to be submitted again manually.

Start with the attached codex-desktop-276be196-ca36-4422-bdae-1d4b5a46fdc0-46436-t0-i1-000013-0.log and reproduce the queued follow-up flow during a long-running task, including context compaction. Trace why the queued message becomes unavailable, then verify that it remains associated with the conversation and submits automatically after the task finishes.