Query API Returning 429 Error

Question

We're running into an issue where any calls we make to the Query API in Power Automate are returning a 429 "Too Many Requests" error. The detailed error message is "You have reached the limit for how many queries you can add to the queue. Try your request again once other queries have completed." I'm also getting this same message if I try to run a query in web view (although it works it database view).

I believe this issue was originally caused by a PA flow behind our Power BI reports that run into trouble and spawned too many additional flow runs. I've done what I can to try and stop all the runs, but based on this message, I think some flows runs are still happening behind the scenes and have gotten stuck.

Has anyone else run into something like this? Any thoughts as to how to ensure all PA flow runs have stopped and/or see what queries are in the queue? I think the solution here is to clear out the query queue, but I have no idea how to do this. (Support doesn't seem to either.)

James Belich · Answer

Alex, I did test this out on a report as you suggested, but it didn't solve the issue. I just heard back from support and the engineering team was able to clear out the throttled queries that were gumming up the works and my flows appear to be running normally again now (still testing everything out to be sure).

I am going through and limiting the concurrency on the PBI reports anyway, to help prevent this issue from happening again, so thank you for the tip!

Alex Wong · Answer

did you limit the concurrency of data refresh in power bi desktop option?

James Belich · Answer

@Jordan Wells @Callum Everhart @Alex Wong Thank you for your replies. I've gone through the previous flow runs and worked to cancel all of the still-running flow runs. As best as I can tell, I've gotten them all, but Microsoft's action to cancel flow runs in bulk in Power Automate does not seem to work correctly, so that's been a challenge. Everything that would trigger these flows (i.e. the automatic refresh of our Power BI reports) should be turned off and I haven't seen any new flow runs save my own tests. However, it's been days since I turned everything off and the issue persists, so I don't think this is something that's going to clear out on its own.

I did spend a couple hours on the phone with Blackbaud support to try and move this forward (despite the urgency of the issue, no progress has been made in now almost three business days) and will continue to work with them. I did speak with someone more senior in support who did imply that I'm not the only one to have experienced this issue.

@Alex Wong Thanks for the reminder about tomorrow's PA user group. @Erik Leaver if this is something we can look at, it would be much appreciated. At present, I'm working to create some stopgap reporting so that we can keep our processes moving forward while we await a resolution from Blackbaud.