Azure Content Understanding API Taking Excessive Time (Timeout Issue) - Custom Analyzer

Question

Azure Content Understanding API Taking Excessive Time (Timeout Issue) - Custom Analyzer

Miguel Gomez 5

Service: Azure Foundry > Content Understanding > Analyzer Model

Issue Description:

We're experiencing a significant performance difference when using the Content Understanding Analyzer model between the Azure Web Console and the API endpoint.

When using the Azure Web Console, the model processes the same file consistently within 5–10 seconds.

When invoking the same analyzer via the API endpoint, Sometimes, the response time exceeds the 120-second timeout limit.

Even after extending the timeout to 320 seconds, the API call still fails to return a JSON response.

Steps to Reproduce:

Upload and process a file using the Azure Web Console – completes in ~5–10 seconds.

Send the same file to the Analyzer model via the API – results in timeout (>120s and >320s).

Expected Behavior:

The API endpoint should process the file with similar performance to the Web Console or within acceptable API timeout limits.

Actual Behavior:

The API call does not return a response within even 320 seconds.

Request for Support:

We would appreciate your assistance in identifying the cause of this performance discrepancy and guidance on how to resolve or optimize API response times.

santoshkc 15,435 Reputation points Microsoft External Staff Moderator

2025-07-01T10:24:21.1866667+00:00

Hi Miguel Gomez,

We understand the concern regarding the performance discrepancy between the Azure Web Console and the API endpoint for the Content Understanding Analyzer. The Web Console often runs jobs in an optimized environment with managed retries and backend optimizations that might not reflect the same behaviour in API calls.

The timeout issues you're facing via API could be related to factors like payload size, network latency, request concurrency, or backend resource allocation. We recommend check your file size or content complexity affects the API call.

I hope you understand! Thank you.
santoshkc 15,435 Reputation points Microsoft External Staff Moderator

2025-07-01T13:34:14.1733333+00:00

Hi Miguel Gomez,

Following up to see if the given response was helpful. In case if you have any resolution, please do share that same with the community as it can be helpful to others.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-02T16:36:58.43+00:00

Hi Miguel Gomez,
Did you get any chance to check the response. Thank you!
Miguel Gomez 5 Reputation points

2025-07-03T01:48:17.1466667+00:00

Hi guys,

I did see the response but it doesn't really help us that you have an optimised environment that is difficult to replicate with the API. Without the consistency (Sometimes it runs fine, other times with the timeout), it is difficult to leverage this service in new workflows.

Our payload has been limited to one document (<2mb as we're testing still) so this shouldn't be an issue. It would consist of a 1-2 pages of handwritten text filling out a few fields in a form so I wouldn't consider it very complex. We were also looking to see if this could be related to subsciption options, but pricing models for CU services have been difficult to understand and looks like only PAYG.

Are there any other options you suggest to better manage network latency or backend resource allocations? Thanks.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-03T11:43:26.76+00:00

Hi Miguel Gomez,
Since your document size is small and content is simple, the API timeouts you’re experiencing are likely due to backend resource allocation or transient issues rather than payload complexity. The Azure Web Console runs in a managed and optimized environment, which can lead to faster and more consistent results than API calls. To reduce latency and improve reliability, ensure you're using the regional endpoint closest to your environment, avoid sending multiple concurrent requests at once, and implement retry logic with exponential backoff. While Content Understanding is only available under the Pay-As-You-Go pricing model, there are no special performance tiers, but backend performance can still vary depending on service load.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-04T12:29:04.1866667+00:00

Hi Miguel Gomez,
Did you get any chance to check the response. Thank you!
Rohan Shah 0 Reputation points

2025-07-10T15:14:58.8533333+00:00

Hi @Pavankumar Purilla , @santoshkc I am facing similar issues. Approximately 70% of my requests (single document per request) get timed out. All my documents are < 2mb in size. However, I do have multiple users make concurrent requests to the service. Please suggest ways to optimize the backedn service performance.

Your answer

santoshkc 15,435 Reputation points Microsoft External Staff Moderator

2025-07-01T10:24:21.1866667+00:00

Hi Miguel Gomez,

We understand the concern regarding the performance discrepancy between the Azure Web Console and the API endpoint for the Content Understanding Analyzer. The Web Console often runs jobs in an optimized environment with managed retries and backend optimizations that might not reflect the same behaviour in API calls.

The timeout issues you're facing via API could be related to factors like payload size, network latency, request concurrency, or backend resource allocation. We recommend check your file size or content complexity affects the API call.

I hope you understand! Thank you.
santoshkc 15,435 Reputation points Microsoft External Staff Moderator

2025-07-01T13:34:14.1733333+00:00

Hi Miguel Gomez,

Following up to see if the given response was helpful. In case if you have any resolution, please do share that same with the community as it can be helpful to others.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-02T16:36:58.43+00:00

Hi Miguel Gomez,
Did you get any chance to check the response. Thank you!
Miguel Gomez 5 Reputation points

2025-07-03T01:48:17.1466667+00:00

Hi guys,

I did see the response but it doesn't really help us that you have an optimised environment that is difficult to replicate with the API. Without the consistency (Sometimes it runs fine, other times with the timeout), it is difficult to leverage this service in new workflows.

Our payload has been limited to one document (<2mb as we're testing still) so this shouldn't be an issue. It would consist of a 1-2 pages of handwritten text filling out a few fields in a form so I wouldn't consider it very complex. We were also looking to see if this could be related to subsciption options, but pricing models for CU services have been difficult to understand and looks like only PAYG.

Are there any other options you suggest to better manage network latency or backend resource allocations? Thanks.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-03T11:43:26.76+00:00

Hi Miguel Gomez,
Since your document size is small and content is simple, the API timeouts you’re experiencing are likely due to backend resource allocation or transient issues rather than payload complexity. The Azure Web Console runs in a managed and optimized environment, which can lead to faster and more consistent results than API calls. To reduce latency and improve reliability, ensure you're using the regional endpoint closest to your environment, avoid sending multiple concurrent requests at once, and implement retry logic with exponential backoff. While Content Understanding is only available under the Pay-As-You-Go pricing model, there are no special performance tiers, but backend performance can still vary depending on service load.
Pavankumar Purilla 8,665 Reputation points Microsoft External Staff Moderator

2025-07-04T12:29:04.1866667+00:00

Hi Miguel Gomez,
Did you get any chance to check the response. Thank you!
Rohan Shah 0 Reputation points

2025-07-10T15:14:58.8533333+00:00

Hi @Pavankumar Purilla , @santoshkc I am facing similar issues. Approximately 70% of my requests (single document per request) get timed out. All my documents are < 2mb in size. However, I do have multiple users make concurrent requests to the service. Please suggest ways to optimize the backedn service performance.

Share via

Azure Content Understanding API Taking Excessive Time (Timeout Issue) - Custom Analyzer

Your answer