Any attempt to upload any file to any vector store in OpenAI Resource in Germany West Central Region is throwing an internal server error and leaving status "Indexing Failed"

David Captur 175 Reputation points
2026-07-14T07:22:27.54+00:00

Any attempt to upload any file to any vector store in an OpenAI Resource in Germany West Central Region is throwing an internal server error and leaving status "Indexing Failed".

This problem is occurring for almost all files, of different formats, in all vector stores and both when trying via screens OR via the API. Any attempt to upload results in this:

User's image

This is not a temporary / new issue, it has been going on for several weeks. The same identical approach on a different region for the same files, same setup works without problems. It seems to be something region specific as other non-prod resources on the same region have the same problem.

Azure Files
Azure Files

An Azure service that offers file shares in the cloud.

0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest
  1. Alex Burlachenko 25,285 Reputation points MVP Volunteer Moderator
    2026-07-14T07:50:31.03+00:00

    hi David Captur & thx for sharing urs issue here at Q&A portal,

    fact that even a simple .txt file fails with 'Indexing failed An internal error occurred' makes it very unlikely that this is related to document parsing or file format.

    Combined with what you've described the issue reproduces in both the portal and the API, it affects multiple vector stores

    it has persisted for several weeks, the same files and workflow succeed in other Azure OpenAI regions, this strongly points to a region-specific backend issue with the vector indexing service in Germany West Central.

    At this point, I'd stop troubleshooting the client side and will escalate it (as a moderator) but be rady to provide them Azure OpenAI resource name + Region (Germany West Central) + Vector store ID(s) +File ID(s) & Approximate timestamps of failed uploads + x-ms-request-id / x-ms-client-request-id from the API response (if available)

    Since even a minimal text file produces the same internal error, it doesn't appear to be caused by unsupported file types or document content. The fact that the identical workflow succeeds in another region makes this look like a backend issue specific to the indexing service in Germany West Central that will need investigation by the product team.

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

    and at my blog https://ctrlaltdel.blog/

     

    Was this answer helpful?

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.