Repository navigation
json with "oneOf" as root causing error for azure openai endpoint #30132
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.623.30605
What platform is your computer?
Failed on two computer: Darwin 27.0.0 arm64 arm, Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
I've been using azure openai endpoint, when codex calls certain tool, I get this error:
Invalid schema for function 'automation_update': schema must be a JSON Schema of 'type: "object"', got 'type: "None"
The issue is probably caused by the oneOf field in the automation_update tool definition, which Azure OpenAI does not support:
https://learn.microsoft.com/en-us/azure/foundry/openai/how-to/structured-outputs?tabs=python-secure%2Cdotnet-entra-id&pivots=programming-language-csharp#json-schema-support-and-limitations
What steps can reproduce the bug?
use azure openai endpoint and ask codex to run a bunch of tools, and very likely you'll see this error
Additional information
No response
Reacted by Kevin Bao, XYD, Xingyu Jin, xiaolvdou, Alexander Brasil, Thiru Kumaran, Alexey Levin, Justin D. Harris, Mark Music, Chukwuebuka Sunday Onah and 9 more
Reacted by Shiki, Pablo, Xingyu Jin, hendrik-101 and Ruotian Pang
Activity
Carlo9013 commentedon Jun 26, 2026
I've also had this same issue with version 26.623.12021
thiagoperes commentedon Jun 26, 2026
This is quite serious, we aren't able to use codex any longer @jif-oai @cconger @anp-oai
keith-dell commentedon Jun 26, 2026
Also having the issue on 26.623.31921
notImposterSyndromeIfImposter commentedon Jun 26, 2026
Easy to reproduce. I'm a CLI user/don't use automations myself so excuse the clunky usage. Once a thread triggers the automation it's completely dead. Forking prior to the call does restore functionality.
Break the thread
Fork to Restore
etraut-openai commentedon Jun 26, 2026
This appears to be caused by an out-of-date deployment of code in Azure. The Azure team regularly updates their code to match OpenAI's, but sometimes they lag in their deployment. This problem will likely resolve itself once they redeploy. If you haven't already done so, please report to the folks at Azure. That may help accelerate a fix.
Waffleboy commentedon Jun 27, 2026
There should at least be a warning when updating or fallback code - its quite disruptive and we're caught offguard
thiagoperes commentedon Jun 27, 2026
Still ongoing
Waffleboy commentedon Jun 29, 2026
For those who are affected and can't wait for them to fix this issue - download an older version here https://github.com/nooblyf/codex-releases/releases/tag/2026-06-12
TreeOfLearning commentedon Jun 30, 2026
@etraut-openai It worked before with older versions of codex (see comment above, 2026-06-12 is fine). Is there any reason why a fallback can't be added to this codebase so that threads don't get "bricked" in the event of an outdated API?
DreamstarDS commentedon Jul 1, 2026
need fix
IamLizu commentedon Jul 1, 2026
On 26.623.81905, with Azure OpenAI provider.
trrwilson commentedon Jul 1, 2026
Sharing from the AOAI/Foundry side at Microsoft, the problem's been root-caused and a fix is rolling out ASAP.
As @etraut-openai described, this stemmed from a recent (last few weeks) extension of Responses API non-strict schema support not yet being fully reflected in AOAI's configuration.
We're following up to see how we can better coordinate to catch these issues sooner. It's a particularly tricky class of problems: extended schema component support within schema payload is a lot more subtle than new, typed properties on an API, and that makes it tough for both defensively handling it (in Codex) as well as comprehensively anticipating it (in 1-to-1 AOAI support). Tricky or not, though, it's important.
david-liang commentedon Jul 2, 2026
same here.
yidasanqian commentedon Jul 2, 2026
same 。trace
welsonsxc commentedon Jul 6, 2026
I am broken. I am helpless. I am exhausted. I am silent
Ahmet-Dedeler commentedon Jul 15, 2026
guys the issue still exists, whats going on? using gpt 5.6 sol via azure
Waffleboy commentedon Jul 15, 2026
Quoting my reply for those who just scrolled to the end. Older releases still work.
Ahmet-Dedeler commentedon Jul 15, 2026
Confirmed this is still failing on July 15, 2026, and reproduced it directly against Azure's Responses API (so this is not just a Codex client/thread issue).
Environment:
26.707.72221gpt-5.6-sol/ GlobalStandard (model version2026-07-09)POST /openai/v1/responses, Entra bearer authMinimal result:
parameterswith a top-leveloneOf-> HTTP 400:Invalid schema for function 'automation_update_repro': schema must be a JSON Schema of 'type: "object"', got 'type: "None"'.{"type":"object", ...}-> HTTP 200.Failing request IDs for Microsoft to trace:
x-request-id: 116b61d6-f9d8-9de2-86c9-194a8ee7dcb6apim-request-id: 2ddfab1f-841c-4ac4-9080-9a0d8b38fabdEast US2026-07-15 07:00:45 UTCSo the rollout mentioned on July 1 either has not reached this East US path/current model stack, or this has regressed. A local proxy that rewrites top-level
oneOfinto an object schema unblocks Codex, but users should not need that workaround.@trrwilson could the Azure team check the request IDs / rollout status? Please keep this issue open until the direct API reproduction succeeds without schema rewriting.
Rsirp0c commentedon Jul 15, 2026
@Ahmet-Dedeler Thanks for your feedback, this is indeed failing again on gpt-5.6-sol. I'm working with azure team on this!
Rsirp0c commentedon Jul 16, 2026
@Ahmet-Dedeler gpt-56-sol is fixed. Let me know if you're still seeing other issues
[-]automation_update tool json start with "oneOf" causing error for azure openai endpoint[/-][+]json with "oneOf" as root causing error for azure openai endpoint[/+]Rsirp0c commentedon Jul 26, 2026
Everyone, seems like this problem is stable now. Closing the issue!