Please trace Azure Responses API HTTP 500 (gpt-5-mini, East US)

Nhlanhla Nyembe 0 Reputation points
2026-11-16T19:04:07.8966667+00:00

I’m troubleshooting repeated HTTP 500 errors from the Azure OpenAI Responses API on a gpt-5-mini test deployment. The API generates a short narrative for a Word report in a local Django application. The test sends only synthetic registration totals. An earlier live test generated the Word draft successfully.

Deployment and request

  • Azure OpenAI resource region — East US

Deployment — gpt-5-mini, Global Standard, model version 2025-08-07

API route — POST /openai/v1/responses on the resource’s .openai.azure.com endpoint

The request sets store to false and max_output_tokens to 1200.

What I observed

The standard Word report downloads successfully. The AI Word export fails and Django returns HTTP 502 to the browser.

I called the same reporting function directly from the Django shell with a small synthetic input of 10 submissions, 7 activations, and 3 pending registrations. The Azure API repeatedly returned HTTP 500. The diagnostic captured a request ID but showed no Azure error code or message. The captured failure occurred on 15 November 2026 at approximately 16:50 UTC (18:50 SAST).

A separate test in the Microsoft Foundry Chat playground on the same deployment returned HTTP 400 and displayed a trace ID.

Azure Service Health showed no active service issues when I checked after the failure.

What is the best way to narrow down this HTTP 500 when the response provides no error details? Is there a recommended minimal Responses API request or a resource-level diagnostic I can run to isolate the problem? I’d also appreciate guidance on whether the Foundry playground HTTP 400 warrants a separate investigation.

I can share the Azure request ID and playground trace ID privately if needed.I’m troubleshooting repeated HTTP 500 errors from the Azure OpenAI Responses API on a gpt-5-mini test deployment. The API generates a short narrative for a Word report in a local Django application. The test sends only synthetic registration totals. An earlier live test generated the Word draft successfully.

Deployment and request

Azure OpenAI resource region — East US

Deployment — gpt-5-mini, Global Standard, model version 2025-08-07

API route — POST /openai/v1/responses on the resource’s .openai.azure.com endpoint

The request sets store to false and max_output_tokens to 1200.

What I observed

The standard Word report downloads successfully. The AI Word export fails and Django returns HTTP 502 to the browser.

I called the same reporting function directly from the Django shell with a small synthetic input of 10 submissions, 7 activations, and 3 pending registrations. The Azure API repeatedly returned HTTP 500. The diagnostic captured a request ID but showed no Azure error code or message. The captured failure occurred on 15 November 2026 at approximately 16:50 UTC (18:50 SAST).

A separate test in the Microsoft Foundry Chat playground on the same deployment returned HTTP 400 and displayed a trace ID.

Azure Service Health showed no active service issues when I checked after the failure.

What is the best way to narrow down this HTTP 500 when the response provides no error details? Is there a recommended minimal Responses API request or a resource-level diagnostic I can run to isolate the problem? I’d also appreciate guidance on whether the Foundry playground HTTP 400 warrants a separate investigation.

Azure OpenAI in Foundry Models
0 comments No comments

2 answers

Sort by: Newest
  1. Nhlanhla Nyembe 0 Reputation points
    2026-11-19T18:43:44.7466667+00:00

    Thank you, Mariem. I checked Azure Service Health and saw no active incidents. The East US deployment still returned HTTP 500 when I sent a simple Reply with OK request using the documented Responses API route and headers.

    I’ll run the same request against West US 3 and post the results here. If both fail, is there a resource-level diagnostic you recommend? I can share the request IDs privately if helpful.

    Was this answer helpful?

    0 comments No comments

  2. Mariem Moalla 81 Reputation points MVP
    2026-11-16T22:34:43.1633333+00:00

    Normally an HTTP 500 error indicates an internal server error when calling the Azure Responses API (GPT-5-mini model).
    This can be caused by temporary backend issues, malformed requests, or regional service disruptions.

    First, validate your request payload and headers against the Azure OpenAI API specifications.

    Next, check Azure Service Health for any ongoing issues. If no issues are reported, try sending the request to a different Azure region.

    Was this answer helpful?

    0 comments No comments

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.