Forum Discussion
Unable to Refresh multiple (API) Web Queries that all use the same offline access token
I have a PowerBI Desktop file that has 17 power queries and all of them request the same server "www.example.com/graphql/..." with the same offline access token (p.s. the server uses Keycloak for authentication/authorization).
This is an example of one of the 17 queries API calls:
But the problem is when I click on refresh to refresh all of these queries it starts loading for like 3-10 minutes (based on internet speed and server load I assume)
And after waiting one of two happens.
either it refreshes all the data correctly or sometimes it fails due to timeout error:
My question now is how to avoid the timeout error that sometimes happens.
Anonymous
Actually, I was able to find another solution,
I had to disable the parallel loading so that it would send one request at a time:
it seems our server gets busier and slower when processing all of these parallel requests simultaneously, which causes it to hit the 100-second Cloudflare timeout for some of them.
3 Replies
Hi salem_wafi
Try adding a "timeout" parameter in Web.Contents() function. Here is a similar case for your reference
Web.Contents - PowerQuery M | Microsoft Learn
Solved: Query Timeout on update - Microsoft Fabric CommunityBest Regards,
Gao
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!How to get your questions answered quickly -- How to provide sample data in the Power BI Forum
Thanks Anonymous
I tried that, but now it throws 524 because Cloudflare on the server timeout at 100 seconds, and that can't be changed.
Is there a workaround for that?Anonymous
Actually, I was able to find another solution,
I had to disable the parallel loading so that it would send one request at a time:
it seems our server gets busier and slower when processing all of these parallel requests simultaneously, which causes it to hit the 100-second Cloudflare timeout for some of them.
