API request return httpcode 408

Question

API request return httpcode 408

Mofei Zhuang 140 Microsoft Employee

I attempted to call the Purview API from my local code today, but consistently received HTTP 408 (Request Timeout) responses despite multiple retries. I reviewed the troubleshooting guide but couldn't find a solution that addresses this specific issue.

Here is my request : https://PrefTest.purview.azure.com/datamap/api/atlas/v2/entity/bulk?minExtInfo=false&guid=24187c6b-8982-47cd-8754-c1a884ad0779&guid=5449f955-89e1-4e26-b6a2-32b5e46bf79f&guid=4f0d22d1-534d-499c-b0fd-c01b94411325&guid=44a10974-54ef-4207-bfcf-df0fcbae6431&guid=5fb9b1bb-2dfa-4334-9905-1009687ed3f7&guid=8804540a-5d86-4266-aa2f-32fdb976d183&guid=4409aa4d-7c95-4f87-98e8-07db3eb19c8f&guid=260fa16d-c079-43bf-99f1-6fc126b90793&guid=8d58c7a9-87aa-4166-a829-a74d05d1e05a&guid=9602c5f3-9720-4a0f-99b1-295718930edd

Here is the response : {"requestId":"bd0c03cc-edb0-427f-9ef8-29eced7868c2","errorCode":"RequestTimeout","errorMessage":"Request timed out. This could be a transient issue and you may re-run the operation following https://aka.ms/purviewdatamap408 troubleshooting guide. If it fails again continuously, contact customer support."}

0 comments

1 answer

Your answer

Answer 1

Venkat Reddy Navari 5,840 Microsoft External Staff Moderator

Hi Mofei Zhuang Thanks for the detailed report. A consistent HTTP 408 from the Purview /entity/bulk API typically points to a timeout caused by request size, backend latency, or network issues.

Here are troubleshooting steps to try:

Break Large Requests into Smaller Batches: You're querying 9 GUIDs in one call try splitting into smaller batches (2–3 GUIDs) to reduce processing load and isolate any problematic entity.

Run with Diagnostic Tools: Use curl or Postman to measure latency:


curl -v --trace-time --max-time 30 "<your URL>"

Capture traffic via Fiddler/Wireshark to check DNS, TLS, or timeout phases.

Enable Diagnostic Logs: In Azure Portal → Purview > Diagnostic Settings, enable:

AtlasAPIRequests
RequestLatency
ThrottlingEvents

Send logs to Log Analytics for insights into delays or throttling.

Retry with Backoff: Use exponential backoff (e.g., 2s → 4s → 8s) and set a max wait time around 30–60s.

Check Network & Azure Health:

Use Network Watcher to test latency to your Purview endpoint.
Visit Azure Service Health for any incidents in your region.

Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Mofei Zhuang 140 Reputation points Microsoft Employee

2025-07-15T05:30:37.29+00:00

I did some test I think the problem is not on the request URL, because even I just request one Entity by it's guid, it still response me 408 error.

I tried to request an Entity by this API : https://learn.microsoft.com/en-us/rest/api/purview/datamapdataplane/entity/get?view=rest-purview-datamapdataplane-2023-09-01&tabs=HTTP, with only one guid, it return me a 408 error.

Let me give you more context about my scenario :

I created a Custom Entity Def，let's call it Custom_murphy and created a relationship def make it link between Custom_murphy and azure_data_explorer_cluster.

What I did is to create a custom entity and link it to azure_data_explorer_cluster, save all of them into Collection : B

But before this action I had created an entity of azure_data_explorer_cluster in collection A with the same qualifiedName.

So the thing is when I create the custom entity and also the azure_data_explorer_cluster entity in collection B，the previous entity in collection A just disappear.

So now, what I face is I can search the azure_data_explorer_cluster entity in collection B by this API , even I use the guid to search.

But I can see the azure_data_explorer_cluster entity by it's guid from Purview's portal.

So my questions are :

1.How Purview act if I create an entity with the same qualifiedName but in different collection.

2.How can I fix this situation.
Venkat Reddy Navari 5,840 Reputation points Microsoft External Staff Moderator

2025-07-18T19:22:55.3166667+00:00
Hi Mofei Zhuang Thank you for the additional context this helps clarify the behavior you're observing.

Based on your latest findings, here are some key points and guidance:

Clarifying the Behavior with Same qualifiedName Across Collections

Purview Entity Uniqueness:

In Microsoft Purview, qualifiedName is treated as a unique identifier within the entire data map, not just within a collection.

If you create an entity with the same qualifiedName in a different collection, Purview does not allow multiple active entities with the same qualifiedName. Instead, the new entity effectively replaces or supersedes the existing one, depending on the API call and context.

What Likely Happened:

When you created the new azure_data_explorer_cluster entity in Collection B with the same qualifiedName as the one in Collection A, the original entity was overwritten or hidden.

This may result in inconsistent visibility or reference behavior — for example, visible in the UI but not resolvable via API due to internal metadata or indexing conflicts.

Why You're Seeing HTTP 408 (Request Timeout): Since even single GUID lookups are timing out, and especially because the entity exists in the UI but not through the API, this suggests a metadata conflict or corruption caused by the duplicate qualifiedName.

Recommendations to Resolve the Issue

Avoid Duplicate qualifiedNames Across Collections: Update one of the qualifiedNames to ensure uniqueness across your data map you might consider including the collection name in the qualifiedName for disambiguation.

Clean Up Conflicting Entities: If possible, remove or rename the conflicting entity in one of the collections.

Force Re-index: After resolving the conflict, allow some time for Purview to re-index entities, or trigger a metadata refresh if applicable.

Enable Diagnostic Logging: As previously suggested, turn on AtlasAPIRequests, RequestLatency, and ThrottlingEvents under Diagnostic Settings to get more insight into timeout causes.

Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Venkat Reddy Navari 5,840 Reputation points Microsoft External Staff Moderator

2025-07-21T18:36:52.8833333+00:00

Mofei Zhuang Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

API request return httpcode 408

1 answer

Your answer