You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
gpt 5.4 from azure costantly fails with "Item ... of type 'reasoning' was provided without its required following item." #20698
When using OpenCode with GPT 5.4 xhigh provided from Azure Cognitive Services after 1/2 tool calls it returns:
Item ... of type 'reasoning' was provided without its required following item.
This happens both with web ui and TUI
Even saying "continue" it still crash, but if i switch to GPT 5.3 Codex it works again, then switching to GPT 5.4, again the same error
it does the same in codex, i think its a problem of azure foundry, where should we report that?
For the moment, it is better to wait for a response from an OpenCode collaborator; perhaps it is due to the format in which the requests are being sent like this similar issue: #2941
A workaround I have found that works is to add BYOK on OpenRouter, check the "always use for this provider" option, and then disable the other providers that offer the GPT model you are using; this way, you can be certain it only uses Azure and you won't have any cost surprises. As a precaution, also create a key with a 1 dollar budget to limit the damage in case of misconfiguration.
Has anyone else been seeing an unusually frustrating model-level refusal "I’m sorry, but I cannot assist with that request." over the past couple of days on Azure, even after switching from Default v2 to Default guardrails?
Has anyone else been seeing an unusually frustrating model-level refusal "I’m sorry, but I cannot assist with that request." over the past couple of days on Azure, even after switching from Default v2 to Default guardrails?
Yes, on GPT 5 to 5.2 models all the time. On 5.3 and 5.4 almost never.
Has anyone else been seeing an unusually frustrating model-level refusal "I’m sorry, but I cannot assist with that request." over the past couple of days on Azure, even after switching from Default v2 to Default guardrails?
Yes, i solved by creating a new guardrail lowering all the protection to minimum and deploying the model with that custom guardrail
Kinda didnt do much today, tmr I hope to completely fix this, I think something the ai sdk does under the hood is mismatched w/ how other tools like codex handle the azure requests, should hopefully be a straight forward fix.
Hello @rekram1-node , today, in the latest OC Desktop version 4.1.19, I have hit the id error again
"Item with id 'rs_04f64f01bab1b2210069e7a257e6948196aa96bc775fae0c38' not found."
Activity
github-actions commentedon Apr 2, 2026
This issue might be a duplicate of existing issues. Please check:
Please review these issues to see if your problem is already tracked or if there is a workaround available.
riccardo-algorime commentedon Apr 10, 2026
+1
riccardo-algorime commentedon Apr 10, 2026
on high also
AmrAbuElyazid commentedon Apr 11, 2026
+1 on MacOS, GPT 5.4 Azure Cognitive Services
R-udren commentedon Apr 13, 2026
+1, fails on GPT 5.4 and 5.3 Codex from Azure Cognitive Services on all reasoning efforts
riccardo-algorime commentedon Apr 14, 2026
it does the same in codex, i think its a problem of azure foundry, where should we report that?
DanielusG commentedon Apr 14, 2026
For the moment, it is better to wait for a response from an OpenCode collaborator; perhaps it is due to the format in which the requests are being sent like this similar issue: #2941
DanielusG commentedon Apr 14, 2026
A workaround I have found that works is to add BYOK on OpenRouter, check the "always use for this provider" option, and then disable the other providers that offer the GPT model you are using; this way, you can be certain it only uses Azure and you won't have any cost surprises. As a precaution, also create a key with a 1 dollar budget to limit the damage in case of misconfiguration.
AmrAbuElyazid commentedon Apr 14, 2026
Has anyone else been seeing an unusually frustrating model-level refusal "I’m sorry, but I cannot assist with that request." over the past couple of days on Azure, even after switching from Default v2 to Default guardrails?
R-udren commentedon Apr 14, 2026
Yes, on GPT 5 to 5.2 models all the time. On 5.3 and 5.4 almost never.
AmrAbuElyazid commentedon Apr 14, 2026
I haven’t tested the other versions since I’m only using 5.4, but I can confirm it’s happening for me on 5.4 in a very frustrating way
DanielusG commentedon Apr 14, 2026
Yes, i solved by creating a new guardrail lowering all the protection to minimum and deploying the model with that custom guardrail
15 remaining items
DanielusG commentedon Apr 16, 2026
Is there a Pull Request I can reference for a quick look?
rekram1-node commentedon Apr 16, 2026
See linked pr, #22764
rekram1-node commentedon Apr 16, 2026
1.4.7 which is releasing rn will have the patch, plz test and lmk
DanielusG commentedon Apr 17, 2026
@rekram1-node
Rip
DanielusG commentedon Apr 17, 2026
Now I'm trying to reproduce the error with chat content that I can share here.
DanielusG commentedon Apr 17, 2026
@rekram1-node
I managed to reproduce the bug by asking the model to analyze the opencode codebase.
For some reason, I can't post the entire log here, and Pastebin was blocking it as spam.
So i created a gist and a download link. I hope they're okay and useful :)
https://gist.github.com/DanielusG/37f6b34266919fddaadc354824db1d64
session.json
rekram1-node commentedon Apr 17, 2026
hmmm okay ill try to figure out cause there weird
rekram1-node commentedon Apr 19, 2026
Kinda didnt do much today, tmr I hope to completely fix this, I think something the ai sdk does under the hood is mismatched w/ how other tools like codex handle the azure requests, should hopefully be a straight forward fix.
npagare commentedon Apr 21, 2026
Hello @rekram1-node , today, in the latest OC Desktop version 4.1.19, I have hit the id error again
"Item with id 'rs_04f64f01bab1b2210069e7a257e6948196aa96bc775fae0c38' not found."
aKardasz commentedon Apr 22, 2026
Same deal running into this as well.
rekram1-node commentedon Apr 29, 2026
opened a pr that should finally kill this
rekram1-node commentedon Apr 29, 2026
Okay i merged it, should release soon, once it does I'm pretty sure this error wont be possible to replicate anymore.
I will continue watching this issue
R-udren commentedon Apr 29, 2026
Had this issue today with GPT 5.5 from Azure. I will use it a lot tommorow and notify you if something gonna break.
rekram1-node commentedon Apr 30, 2026
Alr well fix has been released so hopefully it works well for everyone