Power Community

Power Community

Do you have multiple developers working on 1 flow in Power Automate?

This post is all about some issues that I ran into yesterday. Multiple developers worked on one flow in Power Automate and my app in Power Apps broke.

When apps break!

It is not uncommon to remove a flow and then readd a flow in your app, when things go wrong. So in my case the flow didn’t want to run and I couldn’t immediately see what was going on. So I removed the flow in question then I readded the flow back into the app only to be given the following error

Unable to ad flow. There was a problem adding your service. Please try again later

There was a problem adding your service. Please try again later

And the Power Platform forums weren’t immediately helpful either. That is not very helpful at all. Maybe some more useful information under the More link?

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate More Details

Still pretty useless. It would be good to see some more details here. In my case I first blamed other connections for this issue. Hopefully one day these error dialogues will include useful clues.

Detailed look at the flow

Originally the flow was created by Lucy Eaver and the flow was working as expected.

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate Flow with connection Reference

The flow was developed within a solution and we have an app, a connection reference and a flow all wrapped up in the solution. So far so good.

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate Solutions with app and flow owned by Lucy

Then another developer arrived and changed the flow by adding another Dataverse action to the existing steps in the flow.

Multiple Developer issue showing multiple connections

Now my app stopped working and decided to take the flow out of the app so that it could be re-added.

And this is where the following error message stopped the flow from working:

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate Unable to add flow

So why can’t we add this flow to the app? We have to connections to Dataverse and each of these connections are owned by different user accounts.

How to fix the multiple developer issue?

I’m first going to have a look at the connection references. The connection used here can be found when editing the connection reference in the solution.

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate image 8

Then find the connection in question (outside the solution) and we could consider here sharing connections. But that doesn’t really solve any problems.

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate image 9

The real problem here is that we have one flow with two connections to the same connector. In this case it is the Dataverse connector but I often see the same with SharePoint, Outlook ar really any other commonly used connector.

Multiple connection references with multiple developers

And the developer adding the steps may not even realise the damage that they are doing to the flow and calling app. Because they only added one small step.

Multiple Developers, the way forward!?

You could consider doing all of the development work under a share account. Or you could make sure that every developer has access to all the connections within the flow. But all of this is not easy.

Do you have multiple developers working on 1 flow in Power Automate? Microsoft Power Automate image 11

In this case I’m not even looking at the mess that could have been created with flows and apps that are not in a solution package.

The first step in this case is to make the app/flow work again. So the easiest way to do this is to make sure that only one of each type connection is used within the flow. Once you have switched over the connections you will find that the flow overview screen will only show for example one Dataverse connection.

Then as a next step you could consider giving every developer their own development environment. When they are done with their work they can then deploy to a central development environment. In this central development environment all the work done by each developer are merged and connections are all owned by a shared account. However this becomes potentially a lot of overhead to get some small development done.

This post was originally published on this site

- Advertisement -spot_img

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisement - Advertisement

Latest News

Embed Python Visuals in Power BI Desktop – Quick Review

Hi Folks, This post is all about embedding Python visuals in Power BI, you will need to install the respective...

More Articles Like This

- Advertisement -spot_img