PowerApp triggered Flow’s failing for some users — Resolved — Fixed
Problem
Upon working on a PowerApp project for a client I came across issues with PowerApp triggered Flows where a majority of users who had access to the app would get the following error when clicking a button that should trigger the Flow.
“Connection not configured for this service”
The Flow had initially been created under a general user account, one that was not a service account. However once I obtained a service account from the client I made sure to export and reimport this Flow, to make the service account the primary owner of the Flow and attached it to the button in the app, as I didn’t want any password expiration issues which would cause problems with the Flow being unable to run in the future.
When logging into the app as the service account I found that no such error would occur, so I believed this was because it was the primary owner. Therefore it seemed to be that importing an instance of this Flow with the service account as the primary owner had caused this issue. However it was still strange that this error was not affecting a handful of users as you’d expect it to be something consistent for all other users.
What I tried
When looking online at the Microsoft Flow forums, possible solutions posted by users ranged from the following:
⦁ Exporting and re-importing the Flow again which would hopefully reset the connection
⦁ Deleting the connections within the Flow that was a problem and recreating it.
⦁ Doing general app cleanup by removing any unused Flows
⦁ Removing Version numbers from the Flow name
⦁ Importing the Flows under a new name with the primary owner being the service account
None of the above suggested solutions were able to resolve the error on the PowerApp, additionally logging a support call with Microsoft about this also led to a dead-end.
Solution
I had deemed this error to be occurring as a result of a connection issue, it seemed most likely that when re-importing the Flow into the app under the guise of the service account it had managed to keep the old connections to the Flow which was created under a general user account.
However as mentioned above attempting to reset the connections didn’t seem to solve the issue, this led to me doing the below which resolved the issue -
1. Navigate to the PowerApps dashboard using the service account
2. Find your app and click the Export Package option
3. Make sure to select “Create as New” next to each Flow
4. Select export and a zip file will be created for your app
5. Navigate back to the PowerApp dashboard and select the import canvas app button in the ribbon
6. Browse for the Zip file and once it gets processed you will be allowed to give this app a different name
7. Now make sure to give the Flows a new name by clicking on the spanner icon
8. Once the renaming process has been done click import and a new instance of the app will be created
So I now had two instances of the app and when testing the newly copied app the Flow was now running with no issues present! Therefore, the import process was able to reset the connections and bind them to the service account, which is something I believed it was not doing before even when explicitly deleting and recreating connections within Flow.
What I learnt
⦁ Have the service account ready before starting development on the app
⦁ Avoid trying to change the primary owner of a Flow that has already been attached to the app when using the import and export process within Flow.
