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 moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
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.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 9 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 48 | |
| 27 | |
| 25 | |
| 24 | |
| 22 |