PowerApps button to trigger Flow doesn't work for users

[sts]

I've created a simple app in PowerApps and want to have that app trigger a flow when a user clicks on a button in the app (similar to what’s described in this video). When I, the creator of the app and flow, click on the button in PowerApps, it works exactly as intended. However, when other users click on the button, PowerApps throws an error (see attached image PowerAppErrorBar.png). The error seems to be occurring within PowerApps since it doesn’t look like Flow even registers the request (no record shows up in Flow at all). I’ve given full edit access in both PowerApps and Flow to multiple users, but this hasn’t resolved the issue.

It seems like the problem might be with the connector in PowerApps. One of users took a screenshot showing that the data source for the connection to Flow was listed as "Not connected" (see attached image "PowerAppsDataSourceNotConnected"). This is not what I see as the creator of the app (see attached image "PowerAppsDataSourceConnected"). The users have accepted the connections that they're prompted with at the start, and I've been able to have users successfully send emails through the PowerApps Office365.SendEmail function, so I'm not sure why a connection is not being established for this particular connector.

Any idea why the PowerApps button doesn't trigger the flow for my users? Is there something I need to do to enable the connector for them? I've read numerous forum posts on this topic, but none seem to deal with the problem I'm experiencing. Also, if it's any use, we're on a GCC tenant. 

Let me know if there's any other information I can provide.

[Pstork1]

Here's what I expect is the root of the issue.  When a Flow is invoked by a PowerApps button the Flow runs in the context of the PowerApps user. That means the PowerApps user need permission to the data sources used in Both PowerApps and Flow.  Even if this permission is granted I've seen an issue occasionally where a connector was added in both PowerApps and Flow, then changed in Flow after a user ran it for the first time and accepted the OAuth prompt in PowerApps for the Flow connector.  Changing the connector in Flow gets it out of sync with the one that PowerApps picked up originally when the button was configured.  In that case the best idea is to delete and recreate the button, which will reassociate the modified Flow.  The user should then be prompted again to accept the OAuth permissions.

[sts]

Unfortunately, this hasn't resolved my issue.

Here are the three different approaches I tried:

1. Deleted the button and recreated it

2. Added new button and new flow starting in PowerApps

3. Created a new flow then tried adding a new button in PowerApps and connecting to the flow

Since this didn't work, does anyone have any other suggestions?

[Jeff_Thorpe]

When PowerApps and Flow get out of sync it is best to remove the Flow data source from PowerApps and then add it back. It sounds like you might have already tried this and if so what does your Flow look like? Also is your Flow using a premium connector where your user might not have the correct license?

[sts]

I tried this by going to the Flows in PowerApps and choosing "Remove from app" and then adding it back (see attached image). If you meant something else, please let me know.

I removed and reapplied two different flows. Both are very simple. One takes a single text input field from PowerApps and sends an email. The other takes the same text input field from PowerApps and adds a SharePoint list item. The user who I'm testing this with has edit permissions to the SharePoint list as well. These flows work exactly as intended when I run the app, but they don't work for anyone I share the app with. 

The app does prompt the user to accept the SharePoint connector, but the same "connection not configured for this service" error continues to appear when the user clicks the button that's supposed to trigger the flow.

I'm not using any premium connectors in Flow. 

[Jeff_Thorpe]

The method you used to remove the data source is what I was referring to. You wouldn't happen to be in a GCC tenant? Have you had the user log into Flow just to make sure there are no issues on that end? Have you tried a simple Flow where there are not connectors in the Flow? If it fails with that type of Flow then you know it has to do with the PowerApps trigger and you may need to submit a support ticket. 

[Pstork1]

You mentioned that you shared the app.  Did you also make sure that the users you shared it with had edit permissions to the SharePoint list behind the App?  

[sts]

To answer your questions:

• We are in the GCC tenant. Are there known limitations for this type of implementation in a GCC tenant?
• I've had the user log into Flow to make sure they have access and can run flows. I've even had one user run one of the flows in question in test mode in Flow itself and it has worked, which leads me to believe it has to do with the PowerApps trigger.
• I did make sure that the users had edit permissions to the SharePoint list as well. 

Given that information, do you think it's best to submit a support ticket or is there any other advice you can provide?

Thanks!

[Jeff_Thorpe]

I heard of related issues with GCC tenants last week but didn't pay much attention since I am not in a GCC tenant. I think at this point it might be worth submitting a ticket.

[sts]

Thanks for the heads up. I'll plan to submit a ticket. If there are any resources you're able to direct me to regarding the issues you heard of last week, that'd be aprpeciated, but no worries if it's not something you have immediately available.