Flow().RUN Error - Connection not configured for this service

[ricchiuto]

I have an app that invokes multiple flows. The app and flows exist in a solution and there are two environments (DEV & PROD). Everything works as expected in DEV, but when I import the solution into PROD, there are two users who get an error when completing the action(s) that invoke these flows.

It works with the service account used to create the solution, it works for two of the users, but for these other two particular users, they see this error consistently. I've tried to update/upgrade, delete/re-add the solution. All of the permissions are identical to the DEV environment.

Any thoughts on what to try?

[charleen]

I have had the same problem. I've tried to add the "App Opener" to the default Org as well as "Basic User" but still didnt work. Its weird because everyone can use it through the Dev Sandbox environment.

Its weird because this security role was not enabled inthe Dev environment:

I have set the Run only to my service account as well:

Even my service account cant run the flow in TEST environment.

I've checked the connector tab in the environment and the flow is using that connector. (or at least it says)

Does anyone have any other ideas? Right now i'm running my Dev environment as my Prod which isnt great..

[Pstork1]

Its not about a specific security role. Its about whether the environment is aware of the user or not. Check your Test environment settings to see if it includes a Security Group. If it does then everyone in that Security group has been added to the environment. Most Production environments don't have a security group and therefore users aren't loaded into the environment.

[charleen]

Hi @Pstork1 

Thanks for your reply, My Dev sandbox environment also doesnt have a security group assigned but the flows work there. Could it be because tis sandbox?

Either way I tried adding a security group to the Test environment and saved but to no avail..

Sitll get the same error:

Not sure if after assigning security group if I have to delete and re import the solutions.

[Pstork1]

Have you checked in the users list in the environment to see if the users are listed?  If not there is an add user at the top of that page where you can add the user to the environment and assign them a security basic user security role. That is normally enough.  Usually that happens when the environment is created if you add a group. Since the environment already exists it may take a day or so to catch up with the new group since group membership is cached.

[charleen]

Yeah all users that i'm testing with are in the users for the environment. strange thing is. I created an app with a button that runs a flow and deployed that in my Test environment and it works.

A strang thing I did find in the solution which is not working properly is that I have Environment Variable and Environment Variable definitition, not sure what the difference are:

there was a depency on the variable from another variable 1C1F9971-ACEA-4D8B-AEA1-8EA42DEE45C4 which I could not find anywhere as well..

These are for the data source connector though and not the flow so i dont think it should matter.

Other than that I couldnt find any reason why it wouldnt work

[Navansh]

The issue was resolved by addressing a situation where the App and flows were initially created separately outside of the Solution. These flows were then integrated into the App, and both were added to a Solution in the Development environment for eventual export to the Production environment as a Managed Solution.

Resolution Steps:

1. In the Development (Source) environment solution:

   • Remove the associated flows from the App.
   • Re-add the flows to the App.
   • Publish the customizations.
   • Export the solution as a managed solution.

2. In the Production (Target) environment:

   • Import the solution again as an update (assuming the solution was previously added but not functioning).

There appears to be a bug where, despite the flows continuing to work in the Source environment, a simple refresh of the flow from within the App in the solution triggers an error in the Source environment. However, if the flows are not refreshed, they continue to function without any errors.