3 people reported

All time, since Sep 14.

Injected function_call_output persisted without call_id breaks threads

“function_call_output for send_message_to_thread is persisted without call_id, breaking any strict Responses API provider”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14997/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 2 a week at the mid-September peak.

Strict Responses API providers reject the entire request once the item is in rollout history, making the thread permanently unusable.

Is this your bug?

Where: Session rollout history
Error text: Failed to deserialize the JSON body into the target type: input: missing field `call_id`
Versions: 0.153.4
Platforms: macOS, Windows
How bad: Stops work: a core feature can't be used.

Original reports3, newest first

Sep 29, 2026Automation turns persist function_call_output without call_id, permanently breaking sessions on strict Responses endpointsOn GitHub#49173
Sep 16, 2026function_call_output for send_message_to_thread is persisted without call_id, breaking strict Responses API providersOn GitHub#45914
Sep 14, 2026Standalone injected function_call_output is rejected by strict Responses providers; adding a call_id is not a sufficient repairOn GitHub#45450

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.