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
I have a dataflow that is getting data from an API. Sometimes the dataflow fails for reasons such as one of the services (the API or Azure) being unavailable. The failure has occured once each on consecutive weekends during a scheduled refresh. I can just ignore these refresh failures, perhaps even de-schedule the weekend refresh. The problem I'm having is, after this once off Dataflow failure, the Dataflow turns to this broken state, beyond my control and anything I've done, it starts to say the credentials are incorrect, even though they're not, and will auto-fail thereafter. And the only way it is; re-edit the Dataflow, clear credentials (both my 3rd party API and Azure connections are 'anonymous'). Sometimes that's not even enough. Sometimes I have to change the underlying Power Query superficially, without changing its function or output, just so Power BI unbreaks from its bugged state.
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
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 | |
| 11 | |
| 7 | |
| 6 | |
| 6 |
| User | Count |
|---|---|
| 34 | |
| 26 | |
| 22 | |
| 21 | |
| 21 |