Unanswered

Error 0x80072322: Number of requests exceeded the limit of 6000 over time window of 300 seconds

(0) Share

Report

Posted on by adminlz

Hi!
since the beginning of April 2019, I have been suffering with the same error during data integration between excel and cds using powerquery. I need to update daily about 42 thousand records, but due to this failure, between 100 and 500 records present errors.

I would be very grateful if anyone had any idea on how to solve this problem.

This is the error:

{"error":{"code":"0x80072322","message":"Number of requests exceeded the limit of 6000 over time window of 300 seconds.","innererror":{"message":"Number of requests exceeded the limit of 6000 over time window of 300 seconds."

Best regards,

João

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (8)

Answers (0)

v-monli-msft on at

Like (0)

Report

Hi @adminlz ,

Did you use PowerApps during this process? This is PowerApps community and it seems that you didn't mention anything about PowerApps in your post.

Regards,
Mona

Was this reply helpful? Yes No
adminlz 4 on at

Like (0)

Report

Hi Mona,

Yes, I did. I've been using CDS with PowerApps. The problem is exactly not having the correct database for our apps as a consequence of the problem that I mentioned.

Best regards,

João

Was this reply helpful? Yes No
David Jennaway 716 on at

Like (0)

Report

I think you're hitting the Dynamics 365 throttling limits (though the numbers in the message are slightly different. This article gives more information and also some workarounds. However, the workarounds are mostly how to handle the throttling message in code, and I don't know if you'll be able to apply this with your import via PowerQuery.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @adminlz,
Have you ever solved 0x80072322 error? I hit the same issue in my Dynamics 365 environment, and would love you to share workaround if you could manage.
Thanks,
Toshi

Was this reply helpful? Yes No
David Jennaway 716 on at

Like (0)

Report

I've not found any useful workarounds when using PowerQuery; the only effective workarounds are when you control the calling code, and you capture the error and effectively throttle your code

Was this reply helpful? Yes No
Dawidvh 1,346 on at

Like (1)

Report

This error makes Data Flows pretty useless for most environments. How can importing of data be limited to 6000 rows, Excel can handle 1 000 000 rows, but importing enterprise data into CDS (which doesn't come cheap) only 6000? That doesn't make sense at all.

Was this reply helpful? Yes No
Satish1024 279 on at

Like (0)

Report

Please upvote my idea of removing API throttling limits in the Dataflows
https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Remove-Service-Protection-API-throttling-limits-for-Dataflows/idi-p/484654#M29784

Was this reply helpful? Yes No
Ballzer0 53 on at

Like (0)

Report

im expiriencing the same issue. its so sad because PowerQuery is an amazing integration tool, but all the efforts are useless if you cant trust that all your rows got imported

Was this reply helpful? Yes No