I’m seeing a frequent failure when calling the Responses API that looks like a client-side body timeout even though the API returns 200 OK. Stack Node.js (v22, using built-in fetch and undici) ai@6.0.7 @ai-sdk/openai@3.0.2 @ai-sdk/provider-utils@4.0.2 Model: gpt-5.2-2025-12-11 Wha…

Hey all! I sincerely apologize for the delay, there was an issue preventing us from rolling this out over the last few days. We’re resuming the rollout of this feature now, expect it to be fully rolled out within the next 4 hours

Hey everyone, Apologies for the inconvenience. Our team is taking a look into this issue. We will provide an update as soon as we identify the issue. Thank you!

I suspect this is the underlying issue causing the error we’re seeing here because Agents SDK uses Responses API by default: [image] Agents SDK -> TypeError: terminated Bugs We use openai-agents-js (default Responses API) to run our Multi-Agent Systems (MAS). D…

Hey all! Steve here from the OAI eng team. My understanding of BodyTimeoutError is that it is the result of a timeout waiting for data on the wire between events. Depending on the nature of your integration, it may be many seconds in between events. Would folks be willing to bump up bodyTimeout to …

Thanks for following up Steve! Our timeout is set to 5 minutes and we still often see this issue — is this expected? I don’t know if increasing our timeout value will resolve this.

[image] stevecoffey: we are shipping a new feature which will push keepalive events into the stream at a regular interval I propose a parameter: heartbeat: int - seconds - sets an interval where whitespace is sent before a json output begins being produced in a non-stream setting, verifying …

As additional context: we observe this issue much more frequently when we are streaming API responses. This also occurs with non-streamed responses, but the occurrence rate is significantly lower.

Any updates? We are still getting many errors which are affecting our platform a lot.

Hey all! We are rolling out heartbeat events this week, I’ll post again here when they’re fully rolled out

Hello @stevecoffey , any update for us?

200 OK from /v1/responses but body times out (UND_ERR_BODY_TIMEOUT)

API Bugs

baki.kucukcakiroglu February 13, 2026, 9:48am 29

Although the frequency has decreased, we are still having terminated error with OpenAI Agents SDK which I believe is related to this issue.

Topic		Replies	Views
Agents SDK -> TypeError: terminated Bugs api , gpt-5 , agents-sdk , gpt-41	1	290	February 16, 2026
Assistants API Streaming Connection Closure Issue Bugs bug , error , assistants-api , streaming	5	363	November 26, 2025
[Assistants API] Issue with gpt-4o: httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read) API assistants-api , gpt-4o	12	660	November 26, 2025
520 errors through the responses API Bugs	5	239	June 8, 2026
Error Internal Server Error: The response ended prematurely. (ResponseEnded) API gpt-4 , bug , assistants-api	2	551	November 26, 2025

200 OK from /v1/responses but body times out (UND_ERR_BODY_TIMEOUT)

Related topics