Share via

Document Intelligence prebuilt-read with api-version=2024-11-30 stuck in "running" (West Europe)

Mr B 0 Reputation points
2025-12-05T17:05:02.62+00:00

Service: Azure AI Document Intelligence (prebuilt-read)

Region: West Europe

API version: 2024-11-30

Since today, the prebuilt-read model with api-version=2024-11-30 is not completing for me in West Europe.

Repro #1 – public test file

Test document (PNG with text):

https://www.syncfusion.com/blogs/wp-content/uploads/2023/10/Performing-OCR-on-a-rotated-page-of-a-PDF-document.png

Working case (older API):

POST https://westeurope.api.cognitive.microsoft.com/formrecognizer/documentModels/prebuilt-read:analyze?api-version=2023-07-31

Content-Type: application/json

Ocp-Apim-Subscription-Key: <redacted>

Body:

{ "urlSource": "https://www.syncfusion.com/blogs/wp-content/uploads/2023/10/Performing-OCR-on-a-rotated-page-of-a-PDF-document.png" }

This returns 202 Accepted and the corresponding analyzeResults call quickly returns:

{ "status": "succeeded", ... }.

Failing case (new API):

POST https://westeurope.api.cognitive.microsoft.com/documentintelligence/documentModels/prebuilt-read:analyze?api-version=2024-11-30

Content-Type: application/json

Ocp-Apim-Subscription-Key: <redacted>

Body:

{ "urlSource": "https://www.syncfusion.com/blogs/wp-content/uploads/2023/10/Performing-OCR-on-a-rotated-page-of-a-PDF-document.png" }

The POST returns 202 Accepted and an operation-location header.

However, repeated GET requests to that operation-location always return:

GET https://westeurope.api.cognitive.microsoft.com/documentintelligence/documentModels/prebuilt-read/analyzeResults/931f46a7-32a1-4cdb-af0c-8e556a3d9e39?api-version=2024-11-30

Ocp-Apim-Subscription-Key: <redacted>

Response (even after 20+ minutes):

{

"status": "running",

"createdDateTime": "2025-12-05T15:30:27Z",

"lastUpdatedDateTime": "2025-12-05T15:30:27Z"

}

The status never changes to "succeeded" or "failed".

My Blob Storage and SAS URLs work fine:

  • I can upload the document to my storage account.
  • I can download the same blob via SAS with HTTP 200 and correct content.

When I switch back to the older API:

POST https://westeurope.api.cognitive.microsoft.com/formrecognizer/documentModels/prebuilt-read:analyze?api-version=2023-07-31

with the same document, the operation completes quickly with status "succeeded".

Question:

Is there a known issue with api-version=2024-11-30 for prebuilt-read in West Europe that could cause operations to be stuck in "running" state?

Can someone from the product team check why operation

never transitions to succeeded or failed?

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

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anshika Varshney 13,305 Reputation points Microsoft External Staff Moderator
    2025-12-18T14:17:29.1666667+00:00

    Hi Mr B,

    Welcome to Microsoft Q&A and Thank you for reaching out.

    It looks like you’ve run into an issue where the prebuilt-read model using the GA API version 2024-11-30 never transitions out of the "running" status in West Europe, even though the same document works fine with the older API version (2023-07-31).

    From what we know about the Document Intelligence service, the 2024-11-30 API version is the General Availability (GA) release of the v4.0 REST API, which includes new features and improvements such as searchable PDF output and broader model support. Microsoft Learn

    Please check the below steps:

    Regional/Service Issues Sometimes specific regions have temporary service disruptions or delays in processing with new API versions. It’s possible that West Europe might be experiencing issues with this GA endpoint. Checking the Azure status page or service health in the Azure portal might help confirm if there’s an ongoing incident.

    1. Differences Between API Versions The older version (2023-07-31) uses the legacy Form Recognizer endpoint structure and completes quickly. The newer 2024-11-30 endpoint has updated internal logic and could behave differently with respect to analysis time or status transitions especially in some regions.

    Polling Behavior With the new API version, ensure your polling loop waits an appropriate interval between status checks. Frequent polling without delay can make it harder to observe correct status progression.

    1. Retry With Fallback As you’ve seen already, falling back to the older API version works reliably for this document. Until the new version’s behavior stabilizes in your region, using the older supported version may be a practical workaround.

    Overall, it seems likely this is a service-side or regional behavior that isn’t specific to your document content especially given that the older API returns success quickly, but the new GA version stays "running" indefinitely.

    Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

    Thankyou!

    Was this answer helpful?

    0 comments

  2. AI answer

    2025-12-05T17:05:21.1733333+00:00

    There may be several reasons why the prebuilt-read model with API version 2024-11-30 is stuck in the "running" state in West Europe. Here are some considerations:

    1. Service Availability: Sometimes, specific regions may experience temporary issues or outages. It would be beneficial to check the Azure status page or any announcements related to service disruptions in the West Europe region.
    2. Model Performance: The new API version may have different performance characteristics compared to the older version. If the document being processed is complex or large, it might take longer to analyze.
    3. Request Limitations: Ensure that you are not hitting any request limits or quotas set by Azure for your subscription, which could affect processing times.
    4. Document Format: Although you mentioned that the document uploads and downloads correctly, ensure that the document format and content meet the requirements specified for the prebuilt-read model.
    5. Polling Frequency: When polling for the status of the operation, it is recommended to wait at least one second between requests to avoid overwhelming the service.

    If the issue persists, it may be beneficial to reach out to Azure support for further assistance, as they can provide more detailed insights into the operation ID and any underlying issues affecting the model's performance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.