Forum Discussion

PA_DA's avatar
PA_DA
Frequent Visitor
1 year ago
Solved

Issue with Power BI Button Not Triggering Power Automate Flow for One User

Hey, I’m having an issue with Power BI and the integration of Power Automate. The button fails to trigger, showing an error message that says "not successful." However, the button works perfectly f...
Need Help
  • PA_DA's avatar
    PA_DA
    11 months ago

    I found the problem !

    Thanks for your suggestions and advice!

     

    The problem was that SharePoint sharing did not work for overlapping tenants.
    Since Power BI's Automate button checks the entire retrieval process to see if all connections can be established, if not, this leads to the so-called error.

     

    The second problem was the license. MS has apparently changed it so that if a Premium connector is used, the user must also have a Premium single license, otherwise the flows will not work.

     

    So Thank you for your respons!! 

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi PA_DA ,

Thanks for testing that and sharing the update. Since the user is able to run a brand new flow without any issues (even without being a co-owner), but still gets the error on the original one despite having co-owner rights, it really sounds like something specific inside that original flow is causing trouble not just permissions.

A couple of things worth double-checking.

  • Any connections used in the flow (like SharePoint, Outlook, etc.): Even if the user is a co-owner, some flows are tied to the original creator’s credentials. It might help to open the flow, check the “connections” section, and have the user re-auth or switch to their own where needed.
  • Any steps that reference the user’s email or profile: Sometimes flows use dynamic content like User().Email, and it can behave differently depending on who triggers it especially if there's a lookup or condition depending on that value.
  • Flow parameters: If the button in Power BI passes parameters, check if those are being received correctly by the flow. One small mismatch can cause it to silently fail.

If none of that helps one workaround that’s worked for me in the past, duplicate the flow (export and re-import), then update the button to call the new one. I’ve seen cases where something gets “stuck” in the connection between Power BI and the original flow for just one user, and starting fresh fixed it. Let us know if anything changes happy to dig further if you’re still stuck.

Regards,
Akhil.