Share via

OpenAI Responses API calls + code interpreter tool have been failing (hanging ) in the past week or so

GS 380 Reputation points
2026-02-22T19:01:15.5666667+00:00

We are starting to see more and more OpenAI responses API calls that have the code interpreter tool never return .. in the past week or so 1 out of 4 in general fall into this category.

I am able to reproduce with Postman.

Some calls do succeed but it is becoming concerning and I am not too sure what the issue is exactly .. is anyone else experiencing this ?
I am seeing this in my dev instance and production instance .. both in the same tenant

I am setting the container type to auto

"tools":[{"type":"code_interpreter","container":{"type":"auto"}}]
Foundry Tools
Foundry Tools

Formerly known as Azure AI Services or Azure Cognitive Services is a unified collection of prebuilt AI capabilities within the Microsoft Foundry platform

{count} votes

2 answers

Sort by: Most helpful
  1. Manas Mohanty 14,990 Reputation points Microsoft External Staff Moderator
    2026-02-27T18:40:21.87+00:00

    Hi GS

    Thank you for sharing the details on support ticket and resource id.

    Concerned engineering ticket associated with support ticket is in mitigated state post remedial action were taken from product group.

    Status - Service is normal at customer side as per last interaction in private message.

    Thank you for your inputs and using Azure services.

    0 comments No comments

  2. divyansh agarwal 160 Reputation points
    2026-02-25T20:44:32.5966667+00:00

    If your code_interpreter runs are hanging, here’s what you should try:

    1. Implement proper polling — keep checking the run status until it reaches completed or failed. Don’t assume the initial call will return final output.
    2. Add a client-side timeout + retry logic for runs stuck in queued or in_progress.
    3. Log request IDs and timestamps (UTC) and check if the issue correlates with peak traffic times.
    4. Test with smaller inputs to rule out long-running or blocking code execution.
    5. If the issue persists (~25% failure rate), open a support ticket and include:
      • Request IDs
      • Model name
      • Region
      • Exact payload

    If it’s happening in both dev and prod, it’s likely backend/container allocation behavior — not your tenant configuration


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.