when running Codex 5.2, sometimes it errors out with: Error: Stream completed without a response.completed event

[Arthur742Ramos]

Describe the bug

Codex 5.2 errors out with Error: Stream completed without a response.completed event sometimes. This error is not retried and stops execution, which is frustrating for long tasks. In my experience, an easy fix is to add retries for this error instead of surfacing the error immediately. Retries usually fix the issue.

Affected version

0.0.384

Steps to reproduce the behavior

There is no specific way to reproduce it. It usually happens when copilot is running Codex 5.2 xhigh for long running tasks.

Expected behavior

The expected behavior is to not surface this error immediately to the user and stop the execution. I'd expect retries attempts, since they usually fix the issue.

Additional context

No response

[dereklegenzoff]

Thanks for reporting this. We're seeing elevated error rates with gpt-5.2-codex and we're actively investigating.

[dereklegenzoff]

We just deployed a fix and error rates are back to normal levels. Apologies for the inconvenience and thanks again for reporting this!

I'm closing this issue out for now but please feel free to create a new issue if you run into any more problems.

[Lesiuk]

Just got this error so your fix is clearly not working.

[Arthur742Ramos]

I am also seeing this error happening sporadically. The internal errors that were plaguing the model yesterday are indeed gone, which is awesome, but I believe this is a different root cause.

[dereklegenzoff]

I'll re-open this issue given this does seem to be a slightly different failure mode than what was fixed yesterday.