This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
It would be useful to have refresh logic that would allow the scheduling of multiple refreshes for a report (currently available) where once one of the refreshes was successful then the remainder of the refreshes would be ignored for a period of time. We have situations where we want to refresh a report once a day but due to internal issues the refeshes may not be counted on to always complete. As a result we schedule multiple refreshes of the same report over the day with the expectation that one of them will be successful (due to variations innework latency as the day progresses). In this scenario we could have multiple successful refreshes during a 24 hour period when only one successful refresh is needed and those that follow are "wasted" and a drain on system performance. To be able to ignore follow-on refreshes once one is successful during that time period would be favorable.
I would check out the PowerShell API for the Service. Also, Power Automate:
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 49 | |
| 32 | |
| 27 | |
| 21 | |
| 20 |