Share
Report
36Hi,
We have created an app which has four flows within out development environment. This has then been exported as an managed solution and imported into our test environment. When we conducted some basic testing with our own accounts and test id's the flows worked as expected. However during user testing one of the users consistently got the 'Connection not configured for this service' message.
The flows were created from within the solution (so are solution aware).
We are trying to troubleshoot this but are struggling to find a fix. There doesn't seem to be much logic behind why the flows fail for this particular user, when the flows run for other user's configured in the same way.
I have looked at the other similar posts on the site, pointing to the table permissions for the Basic User role in the environment. The Basic User role in our test environment has Organisation Read on the Process and Solution tables.
The user who cannot run the flows has the 'Basic User' role indirectly assigned through group membership. We have also tried directly assigning the Basic User role just to make sure with no luck.
There is also one suggestion that you need to create an unmanaged layer on the flows but this is definitely not ideal and we want to try and avoid this (as seems to go against best practice).
Can anyone suggest any line of investigation to try and get to the root cause? Any help would be much appreciated, thanks
All responses (
Answers (
