I took my power app that we have been using, and saved it as a new one.
I then reworked the Power App.
I also reworked the Flows it was using before, just kind of cleaning it up.
When testing my new Power App, I have found that a normal user will not kick off the flows I have in the App.
Here is the permissions on the old app that everyone is still using without issues.
Here are the permissions on the new app
So they are the same.
I have NO special permissions on the flows.
When testing in the new App, the bot account (that is my service account I use for the environment and building the apps), it is owner in the App.
When I get to the part where we submit a form and the flows kick off, no issues.
When I test it with my normal account (just a user within the group that has permissions), I can use the App, but none of the flows will kick off (there are three of them).
When I installed the app in Teams and opened it, I did get the box to accept permissions.
I have no clue why this is happening.
I will say, with my old app, I had something similar happen when i was making changes. I ended up having to create a new flow.
Do I need to recreate these flows again?
I exported my flows and App to a different environment.
Removed all the flow connections, and then add them back in.
Same result
I even ran the monitor to see what was happening, but I never see in the monitor it trying to run the flows.
its like it skips them?
@lardo5150 when you say you removed the connections what do you mean by that? Like the connections within the flow? Have you tried to remove the flow from the app and add it again?
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
correct, remoed the connectios from data source, removed references to them in the app, re-added everything.
Same thing.
@lardo5150 that's weird. Have you tried to remove the flow from the app, after that remove the trigger within the flow and Re-create it. Save the flow and at it back to the app.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
User | Count |
---|---|
256 | |
111 | |
95 | |
48 | |
40 |