web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Button Flow Stop Worki...
Power Automate
Answered

Button Flow Stop Working after Export to Managed Solution

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hi,

 

I have a solution that contains a bunch of tables, environment variables, app, flows, etc.

I have a Flow that is using a PowerApps Button as a trigger, collects some information in the app, send it to the flow, creates a file and send back the URL of that file to PowerApps so it can be launched in another tab. This part has always worked fine in my DEV environment for me (User 1) and the a co-worker (User 2).

I exported the solution into a managed on in my UAT environment.

When I (User 1) press the button in the app, it works fine but when User 2 tries to do it, it doesn't even trigger the Flow. It does nothing.

And since this is a managed app, I can't go in edit mode to see if there's an error message or not.

All I know is that it worked for everyone in DEV and now it only works for me (owner of the solution, app and flow).

What could be the problem?

Categories:
I have the same question (0)
  • v-qiaqi@microsoft.com Profile Picture
    Microsoft Employee on at

    Hi @Anonymous,

    Have you solved your problem?

    Do you mean that another co-owner user could not access to the flow when export to another environment?

     

    Actually, a quick fix that you could try is to remove the flow connection from the app and re-add them again. If the issue stays, I think you should check the permission for the User2 in the UAT environment.

    Within Security, select Permission Sets, there is a doc about manage the existing environments:

    https://docs.microsoft.com/en-us/power-automate/environments-overview-admin#manage-your-existing-env...

     

    On your side, please go to the Security Roles List in your UAT Environment, then find the Security Role which is assigned to User2, and open it. Then within the opening Permission panel, check if the Process has assigned full access to the User2.

    vqiaqimsft_0-1636601770415.png

     

  • Verified answer
    Community Power Platform Member Profile Picture
    Microsoft Employee on at

    So here's what resolved the issue. There was multiple issues but it seems to be working now.

     

    1. The user needs to be properly licensed (PowerApps AND Flow Premium) because the button flow uses a premium connector.
    2. The Flow punches out to a SharePoint Library, to which some users did not have the right permissions.
    3. Once the Flow is modified, saved or open, it has to be deleted from the app and re-added again. Then you must save and publish.
    4. The connector of the Word Online got corrupted so we had to remove it and add it back.
    5. The user could not run the flow at all until they were assigned a security role containing "Run Flow" and "Execute Workflow" rights.
      • Note: Once you give those roles, the user will be able to run them. However, the user is still able to run the flow even if those security roles are removed. This is something I still can't explain. I only have to give the role one time and then we're good forever. Makes no sense but oh well...

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 251 Super User 2026 Season 1

#2
Haque Profile Picture

Haque 239

#3
Expiscornovus Profile Picture

Expiscornovus 220 Most Valuable Professional

Last 30 days Overall leaderboard