Item {id} of type 'message' was provided without its required 'reasoning' item

Open 💬 0 comments Opened Jul 14, 2026 by ChrisJCastle93

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

26.707.72221

What subscription do you have?

Enterprise - API pricing

What platform is your computer?

_No response_

What issue are you seeing?

In most threads, my conversations hit an error with a message like:

'Item 'msg_083fb2d2a8606450006a561f65e53c81a4ac2a6903b39cfa05' of type 'message' was provided without its required 'reasoning' item: 'rs_083fb2d2a8606450006a561f629aac81a48c129f085ecd82c7'.'

Codex's understanding is:

In session 019f605f-0fdd-7b43-8a42-399a93460ff8 (Codex 0.144.2), the failing commentary message was persisted at 11:26:47.354Z; its required reasoning item arrived later at 11:26:49.829Z. Every other assistant update in that session has its reasoning item immediately before it. So when Codex reconstructed the next request, it sent the message before its dependency and the API rejected it.
This looks like a race around mid-rollout/commentary updates during tool-heavy work. The required rs_… record is present in the local transcript—it’s just in the wrong order—so the task cannot reliably recover by retrying, compacting, or editing the repo.

This is happening in most threads, after maybe 5-10 messages...

What steps can reproduce the bug?

Feedback ID: 019f6068-25cb-76f3-a7f5-69271006ee55

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗