nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Power BI Refresh Errors

Kelly Hogan

Can anyone help me troubleshoot why a report that previously was refreshing fine is suddenly throwing the following errors:

Refresh

5 queries are blocked by the following errors:

Package

Web.Contents failed to get contents from 'https://defaultc5cf258298024634b115d543513c5a.70.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/0fe3c93541854b408abf332133c52b6f/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=dzfCKDVikro12LZbUTHr32HFFq2knLlT8sSU_kn35eA&authkey=avYF5teMH3synEvHtbkR6JJiqFJGkQfU&queryjson=%7B%22advanced_processing_options%22%3A%7B%22use_alternate_sql_code_table_fields%22%3Afalse%2C%22use_alternate_sql_multiple_attributes%22%3Afalse%7D%2C%22constituent_filters%22%3A%7B%22include_deceased%22%3Atrue%2C%22include_inactive%22%3Atrue%2C%22include_no_valid_addresses%22%3Atrue%7D%2C%22filter_fields%22%3A%5B%5D%2C%22summary_fields%22%3A%5B%5D%2C%22format%22%3A%22Dynamic%22%2C%22gift_processing_options%22%3A%7B%22matching_gift_credit_option%22%3A%22MatchingGiftCompany%22%2C%22soft_credit_option%22%3A%22Donor%22%2C%22use_gross_amount_for_covenants%22%3Afalse%7D%2C%22select_fields%22%3A%5B%7B%22query_field_id%22%3A3001%7D%2C%7B%22query_field_id%22%3A' (502): Bad GatewayCampaignWeb.Contents failed to get contents from 'https://defaultc5cf258298024634b115d543513c5a.70.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/0fe3c93541854b408abf332133c52b6f/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=dzfCKDVikro12LZbUTHr32HFFq2knLlT8sSU_kn35eA&authkey=avYF5teMH3synEvHtbkR6JJiqFJGkQfU&queryjson=%7B%22advanced_processing_options%22%3A%7B%22use_alternate_sql_code_table_fields%22%3Afalse%2C%22use_alternate_sql_multiple_attributes%22%3Afalse%7D%2C%22constituent_filters%22%3A%7B%22include_deceased%22%3Atrue%2C%22include_inactive%22%3Atrue%2C%22include_no_valid_addresses%22%3Atrue%7D%2C%22filter_fields%22%3A%5B%5D%2C%22summary_fields%22%3A%5B%5D%2C%22format%22%3A%22Dynamic%22%2C%22gift_processing_options%22%3A%7B%22matching_gift_credit_option%22%3A%22MatchingGiftCompany%22%2C%22soft_credit_option%22%3A%22Donor%22%2C%22use_gross_amount_for_covenants%22%3Afalse%7D%2C%22select_fields%22%3A%5B%7B%22query_field_id%22%3A31%7D%2C%7B%22query_field_id%22%3A19' (502): Bad GatewayGiftWeb.Contents failed to get contents from 'https://defaultc5cf258298024634b115d543513c5a.70.environment.api.powerplatform.com/powerautomate/automations/direct/workflows/0fe3c93541854b408abf332133c52b6f/triggers/manual/paths/invoke?api-version=1&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=dzfCKDVikro12LZbUTHr32HFFq2knLlT8sSU_kn35eA&authkey=avYF5teMH3synEvHtbkR6JJiqFJGkQfU&queryjson=%7B%22advanced_processing_options%22%3A%7B%7D%2C%22constituent_filters%22%3A%7B%22include_deceased%22%3Atrue%2C%22include_inactive%22%3Atrue%2C%22include_no_valid_addresses%22%3Atrue%7D%2C%22filter_fields%22%3A%5B%5D%2C%22summary_fields%22%3A%5B%5D%2C%22format%22%3A%22Dynamic%22%2C%22gift_processing_options%22%3A%7B%22matching_gift_credit_option%22%3A%22MatchingGiftCompany%22%2C%22soft_credit_option%22%3A%22Donor%22%7D%2C%22select_fields%22%3A%5B%7B%22query_field_id%22%3A649%7D%2C%7B%22query_field_id%22%3A102589%7D%2C%7B%22query_field_id%22%3A9435%7D%2C%7B%22query_field_id%22%3A1051%7D%2C%7B%22query_field_id%22%3A1054%7D%2C%7B%22query_field_id%22%3A2252%' (502): Bad GatewayQuery parameters

Find more posts tagged with

Microsoft Power Platform

Accepted answers

All comments

Erik Leaver

Hi @Kelly Hogan - can you verify the refresh process you are using? I think you are using Power Automate to run some queries. If so, it's likely an issue with the query timing out. Once queries get really large or are being run at peak times, there can be these types of issues.

Kelly Hogan

Yes, using Power Automate query setup from Alex Wong. The Flow appears to be be running successfully. Any ideas on how I can fix this since it has worked fine for so long?

Erik Leaver

@Alex Wong will likely have some good suggestions for you. But I'd start with:

Scheduling your flow off peak time.
Run your queries sequentially
Review your queries & optimize for performance, dropping unneeded fields

Documentation & recommendations for using Query API to sync data:
https://developer.blackbaud.com/skyapi/products/renxt/query/synchronize-data

Kelly Hogan

Thank you for responding quickly!

Kelly Hogan

Dumb question, how would I get it to run the queries sequentially or check to see if it is already doing that? Is that something you can talk me through, Erik or would I be better off asking @Alex Wong?

Alex Wong

not sure if your error message was truncated or not, but if it is not, then your queryjson is not correct, as it only showed:

{
  "advanced_processing_options": {
    "use_alternate_sql_code_table_fields": false,
    "use_alternate_sql_multiple_attributes": false
  },
  "constituent_filters": {
    "include_deceased": true,
    "include_inactive": true,
    "include_no_valid_addresses": true
  },
  "filter_fields": [],
  "summary_fields": [],
  "format": "Dynamic",
  "gift_processing_options": {
    "matching_gift_credit_option": "MatchingGiftCompany",
    "soft_credit_option": "Donor",
    "use_gross_amount_for_covenants": false
  },
  "select_fields": [
    {
      "query_field_id": 3001
    },
    {
      "query_field_id":

So please copy the queryjson info from Power BI parameter and paste here for validation.

Secondly, you want to check the run history of the power automate flow. While the run may say it's successful, there are details you can check to better determine root cause of the issue.

Take some screenshots and provide that here for help on diagnosing.

Kelly Hogan

Alex, there are multiple queries and they all were running fine until Wednesday or Thursday this week. I do not believe I did anything to change them.

Here is a screen shot of the last run of the flow and yes, there is an issue!

Alex Wong

That's exactly the problem, the action to execute the query is failing. even though I don't see the "bottom" part of the action, it is likely a 404 error.

@Erik Leaver This week, I notice that many of my automation that uses the Send HTTP request to blackbaud action to be failing with 404 Not Found when it's used to run query api. This has been working without issue since the beginning of Query API. Once I update the action to directly use the Blackbaud RE NXT Query connector action, it works no problem. I did not report the issue yet to Blackbaud support as I am busy catching up since returning from my 2 weeks vacation.

@Kelly Hogan Erik is likely going to need you to submit a BB support case on this issue before he can get involve to have it fixed, so start with that.

Kelly Hogan

Yes Alex, it says 404, resource not found!

You mentioned in your comment that you updated the action to use the RE NXT Query connector. Is that something I can do, or will I still need to open a ticket with Erik?

Alex Wong

Yes, you can and probably best to update the action and it will fix the issue right away. Opening ticket will help BB identify the issue and fix it permanently, which then you won't need to update this flow or any other flow that may be using the affected action. (this will help many others that may be using the same).

in a nutshell:

replace the BB Send HTTP Post Execute Adhoc Query action with the Blackbaud RENXT Query connector's action Start an ad hoc query job
replace the get job status action with the same connect's action for job status
by replace, you should add the new action first, then make all the changes needed in all subsequent actions, then delete the original action

Kelly Hogan

Thanks so much Alex! I am chatting with support right now to try to get a ticket open. Going to leave my flow alone for now and keep this solution in my back pocket in case there is not a speedy resolution!

Alex Wong

here's a template you

BBQueryAPIDataForPowerBI_20260828163949.zip

can use to "copy" from to update your flow.

Kelly Hogan

Alex and @Erik Leaver, I am guessing I did not ask the right question because here is the response I got from support:

After reviewing the available resources, I would like to inform you that Blackbaud Customer Support is not trained in the use of these tools and is unable to provide assistance with their functionality or troubleshoot errors related to them.
But I still request you to please post the comment in the community post so that our developer will be looking into this

Alex Wong

@Erik Leaver I also open a case for this, just to make it more on the surface for BB to help identify issue and fix

Case #: 021037973

Luis Puesan

If I understand correctly, this is a template to use the BB Query API to insert that data into any Power BI report using the query API tool inside of PBI?

How would you capture exports (unique row per person, data separated into columns) from db view, or since PA only connects to RE NXT webview, exports are not possible as of right now?

James Belich

@Kelly Hogan @Alex Wong @Erik Leaver I'm running into the same issues as Kelly. Like her, I'm using Alex's Power Automate flow to pull data for Power BI reports. All my reports were running fine until late Wednesday night/early Thursday morning when I couple of them starting failing. Digging into the specific flow runs that are failing, I'm also seeing an error in the "BB Send HTTP Post Execute Adhoc Query" action - the output of which shows a 404 error - "Resource Not Found." (My flow looks like the screenshot Kelly posted above.)

What's strange is that this issue seems to be limited to just a couple of my reports. The rest continue to run and refresh just fine. The reports that are having this problem do seem to be the ones that are running more queries, so I wonder if that's also contributing.

Erik, I'd be interested to know more about what you said above about running queries sequentially - is there a way in the Power BI report to prevent the different runs of the Power Automate flow from all happening at the same time? (Which seems to be happening.)

Kelly Hogan

My case # is

021036368

They just emailed me asking for more information. I may need to ask you guys to point me in the right direction if I cannot locate the info!

Alex Wong

tell them to refer to my case # 021037973

Kelly Hogan

Thanks Alex!

Kelly Hogan

Here is what I am seeing as the error when I look today:

Alex Wong

how long did the flow ran?

You have 2-minutes before Power BI (that called the Power Automate flow) s

Kelly Hogan

Alex, I actually implemented the Blackbaud RENXT Query connector's action Start an ad hoc query job yesterday so that I could stop seeing errors and get refreshed reports. So I cannot see how long the flow ran.

Alex Wong

you can always see the run history of the flow as it was when it ran. so updating the flow won't lose that info. However, if you are encountering the error after you made the update, then let's diagnose from there.

James Belich

Just an update to say that I also updated our PA flow to use the Start an Adhoc Query action instead of the Send HTTP Request action. This has fixed the problem for us. I'm still not clear if it's Microsoft or Blackbaud that changed something that caused the previous method to break (at least for some of our reports), but all of our reports are back up and running.

Kelly Hogan

@Alex Wong Just tagging you so you are in the loop too. I did a screen share with Blackbaud yesterday and here is the message I have today:

I wanted to follow up regarding your case after receiving feedback from our internal teams.

We reviewed the information provided and determined that the 404 Resource Not Found response appears to be related to the query ID being referenced in the request. Specifically, we observed that the request is attempting to execute Query ID 1, and we were unable to identify a query with that ID in the environment being tested. Because the query cannot be found, the API would be expected to return a 404 response.

To help us continue the investigation, could you please test the process again using a different query ID that you have confirmed exists in your Raiser's Edge NXT environment?

If the issue persists, please send me:

The query ID used for the test.
- Screenshots of the flow configuration.
- Screenshots of the resulting error message or output.

This information will help us determine whether the behavior is specific to the query being referenced or whether additional investigation is required.

Ian Greenlee

We ran into the same issue on Aug 27th for a flow that was running daily without issue for weeks. Switching from the SKY API's "Send an HTTP Request" to Query's "Start a query job" seems to have fixed it for us as well, so thank you Alex for that solution!

We're looping through 10 queries by folder and were typically getting the 404 error on 2 or 3 calls per run, but the specific requests that failed were not consistent. Some runs it would find a particular query, some runs it wouldn't.

Kelly Hogan

Not sure how important this is anymore other than to know it's better to just switch to the Start Adhoc Query.

Alex Wong

The issue is, I know you are Querying with Adhoc JSON definition, NOT query by id. (unless you also reported running into issue on query by id).

404 makes sense IF you run query by id and gave it an ID that does not exists, however, this DOES NOT applies when it's adhoc query, as there's no "query id to find and not found".

Kelly Hogan

Agreed, I didn't understand where the Query ID was even coming from in their response. I took a peek at both Flows (the updated functioning one and a copy of the old one that was causing errors) and neither seem to specify one anywhere.

James Belich

@Kelly Hogan Are your report still working with the updated flow? I updated our flow last week to the new version @Alex Wong posted, using the "Start an Adhoc Query" action instead of "Send HTTP Request" and it worked fine for several days. However, starting late Monday night, all of our report refreshes started failing again. Looking at the flow runs, I'm getting a 429 error - "Too Many Requests." Curious if anyone else is experiencing this with Alex's updated flow.

Kelly Hogan

James, I am not getting any errors like that right now. Hopefully @Alex Wong will have an idea for you!

Alex Wong

429 means too many requests.

What is important to know is, Power BI send 3 requests per refresh, so if you have a lot of power bi using this method, you will want to schedule them

James Belich

Thanks for the quick reply! It's always helpful to know if others are experiencing the same error.

Kelly Hogan

Totally agree!

"Is this a me problem or a we problem?" LOL!

James Belich

Thanks, @Alex Wong , that's good to know! I only have 7 reports, although one has 10 tables, each of which is running the flow.

Digging into this a little more, I realized that when I updated my flow, I missing setting the timeout values and a limit on the number of retries. I think what happened is that a flow or two must have had issues, and then as those reports kept retrying when other schedule reports started their refreshes, it had a cascading effect. Looking at some of the runs that completed but failed to pull data, they typically ran for over 3 hours rather than the usual 30 to 40 seconds (including as many as 12 retries). I've updated the flow to set a limit on the number of tries now, which is helping (I'm still getting the 429 error, but the run completes in under 5 minutes now).

One strange thing I'm seeing though: I had to cancel a number of the flow runs, as the retries had spawned dozens of runs. However, the flow duration is still incrementing for runs with a status of Cancelled (some runs have a duration of more than 24 hours). This makes me think that even these cancelled runs are still running in the background, and those retries are causing the "Too Many Requests" error.

Alex, do you know of any way to clear out all those old runs so I can start fresh? I think I'll be OK now that I've set some limits.

Alex Wong

there is no way to "clear out" the run history unless to "save as" another flow (which will get a new URL that you need to update in your Power BI)

Make sure all your Blackbaud action (i.e. start adhoc query, get job status) has setting to retry on specific # of times in specific interval of time, not leaving a default retry (which is 8 retry in incremental retry internal, which can take up to 1 hour sometime).

James Belich

Thanks, @Alex Wong. I've gone through and I should now have most if not all of the flow runs truly cancelled. However, I'm still receiving the 429 "Too Many Requests" error. I tried saving a new version of the flow, but it's giving me the same error.

Here's the full error:

{"type":"urn:blackbaud:too-many-requests","title":"Too many requests","status":429,"detail":"You have reached the limit for how many queries you can add to the queue. Try your request again once other queries have completed.","trace_id":"a1dc3b6ef0664f3bbebbeaee5ad0b79b","span_id":"4eec1de3291198e1"}

So maybe I still have some flow instances running that I haven't found yet. Alex, would turning on Concurrency Control help with this at all?

Alex Wong

it sounds like you are doing a lot in 1 power bi.

if one of your reports has 10 tables to load from query, that means when refreshing, you are running 30 query concurrently. I don't think I saw documentation on how many query can be in queue or running at the same time, but guessing 30 may be too much.

You can play around with this setting in your power bi: File → Options and settings → Options
Under Current File → Data Load

James Belich

What's strange is that this has never been an issue before. This particular report worked fine for months without issue until the 404 error above started happening. When I switched to the Run and Adhoc Query action, it worked fine for several days until suddenly failing with the 429 error.

Right now I'm testing on a report that only has two tables, which shouldn't be running too many queries. I'm going to start a case with support and I'll start a new thread if they're not able to help. This is becoming a critical issue for us as we can't go much longer with all of our reports down.

Erik Leaver

Documentation on query best practices notes that

A user may have approximately 20 throttled jobs waiting in the queue at the same time. Environment-level throttling also applies, which means queued jobs can slow or pause when workload in the environment increases.

James Belich

Thanks, @Erik Leaver . Is there a way we can see how many jobs w have in the queue? I've gone through and all the running flows should have been stopped, but it's possible that I've missed a few.

Erik Leaver

@James Belich not that I'm aware of. Support may be able to get that level of diagnostics for you.

James Belich

@Erik Leaver So far their advice has been the same: check how many jobs are in the queue. However, they don't seem to be able to provide any instructions on how to do this.

Jordan Wells

A 502 Bad Gateway usually points to an issue between Power BI and the Power Automate endpoint rather than the report itself. Since several queries are failing at the same endpoint, First check whether the flow is still enabled and running successfully, then test the flow directly. Also verify that the connections and permissions used by the flow haven’t expired or changed. If the flow works normally, checking Power Platform service health and refreshing the Power BI credentials would be my next steps.