Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers!
Enter the sweepstakes now!Prepping for a Fabric certification exam? Join us for a live prep session with exam experts to learn how to pass the exam. Register now.
Hello all,
We have a dataflow that refreshed at 1am on 5/21 as scheduled, and has not refreshed since. Manual refreshes do not register either on the page. There are no errors, nothing to indicate what is going wrong. We did not alter the flow before the issue started, although I did make some changes the morning of 5/21 but it still should have refreshed earlier in the morning. I've made several edits to the flow, saved it, and tried the refresh that pops up there. Still nothing. Here is a not too helpful screenshot since I have no errors to share. Any ideas on what is causing this? I could find no mention of an outage.
Solved! Go to Solution.
Hi, @gbz1
You can try the following troubleshooting steps:
1. Check data source connections: Make sure that all data source connections that the data stream depends on are valid and have not been accidentally changed or disconnected. If the data sources are databases or APIs, make sure that they have not undergone any changes (e.g., password changes, IP whitelist changes, etc.) that might prevent the data stream from accessing them.
2. View the data flow history: In the Power BI service, navigate to the Data Flow page and view the History section. Even if there are no errors, there may be some logs or messages about refresh attempts that may provide clues.
3. Check data flow dependencies: If the data flow depends on other data flows or datasets, make sure that those dependencies are also okay and that they also refresh successfully.
4. Check Power BI service status: Although you said you did not find information about the service outage, it is always good to check the status of the Power BI service again. Sometimes, even small service outages or performance issues can affect a refresh.
5. Check gateway configuration (if applicable): If your data source is on a local or private network and you are using a data gateway, make sure that the gateway is configured correctly and is running.
6. Check Capacity Settings: If you are using Power BI Premium capacity, make sure that the capacity has enough resources to handle refresh requests. The capacity may have reached its resource limit, causing refresh requests to be delayed or rejected.
7 Try to recreate the data stream: If all else fails and you are confident that the problem is not with the data source or configuration, then trying to recreate the data stream may be a last resort. Of course, before doing so, make sure you have backed up all the necessary data and configuration.
I hope these suggestions will help you solve your problem!
Best Regards,
hackcrr
If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly
I encountered the same frustrating issue.
When I hit the dataflow refresh, it spins like it is refreshing, but does not register in refresh history.
When I re entered the data source credentials I saw a quick flash of yellow warning (some thing about HTTPS 2.0?) that went away before I could read it. This was repeatable and so I kept doing it modifying the Privacy Level. It went away after I changed the privacy level from Organzational -> Private.
The dataflow then refreshed successfully and logged it in history. Please note that the dataflow history then showed a number of subsequent refreshes. Apparently the refresh attempts when I had the issue were just queing up until the credential issue was resolved.
----------
Notably, I encountered the issue again on another dataflow.
I went through the steps above an got another error suggesting an issue with the credentials on the data destination. I reentered these credentials and had to tweak/recreate some dataflow steps to redo the credentials as well as update the data destination.
Hi, I have run into this issue twice now during this year. In both cases, the only working solution was to export the dataflow and import it back as another copy. Then replace the old dataflow from the reports/semantic models with this new one. And also in both cases the refresing was done using Power Automate (as a part of a bigger synchronized refresh scheduling).
Hi,
Sometimes schedule refresh option gets disabledand it causes the issue.I recommend you to choose power automate flows for triggering your dataflows and semantic models.
Thanks,
Sai Teja
Hi, @gbz1
You can try the following troubleshooting steps:
1. Check data source connections: Make sure that all data source connections that the data stream depends on are valid and have not been accidentally changed or disconnected. If the data sources are databases or APIs, make sure that they have not undergone any changes (e.g., password changes, IP whitelist changes, etc.) that might prevent the data stream from accessing them.
2. View the data flow history: In the Power BI service, navigate to the Data Flow page and view the History section. Even if there are no errors, there may be some logs or messages about refresh attempts that may provide clues.
3. Check data flow dependencies: If the data flow depends on other data flows or datasets, make sure that those dependencies are also okay and that they also refresh successfully.
4. Check Power BI service status: Although you said you did not find information about the service outage, it is always good to check the status of the Power BI service again. Sometimes, even small service outages or performance issues can affect a refresh.
5. Check gateway configuration (if applicable): If your data source is on a local or private network and you are using a data gateway, make sure that the gateway is configured correctly and is running.
6. Check Capacity Settings: If you are using Power BI Premium capacity, make sure that the capacity has enough resources to handle refresh requests. The capacity may have reached its resource limit, causing refresh requests to be delayed or rejected.
7 Try to recreate the data stream: If all else fails and you are confident that the problem is not with the data source or configuration, then trying to recreate the data stream may be a last resort. Of course, before doing so, make sure you have backed up all the necessary data and configuration.
I hope these suggestions will help you solve your problem!
Best Regards,
hackcrr
If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly
I checked all applicable steps you posted and nothing helped, so unfortunately I just recreated the flow and updated our PBI reports to use the new dataflow.
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
30 | |
27 | |
21 | |
12 | |
12 |