Flow not being triggered after environment copy ?

(0) Share

Report

Posted on by Johns222

Hi all

I have just tried copying over my flow along with related tables to another environment and it does not trigger?

I have tried turning it on/off as well as disabling the environment admin mode. This hasnt worked and it still doesnt trigger.

Im not sure what to do as everything seems to be the same as the environment that it was copied from and I get no error messages.

Thanks for any help

Categories:

Building flows

I have the same question (0)

All responses (10)

Answers (2)

Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

Try removing and re-adding the trigger. I suspect the trigger is tied to the environment it was in and isn't triggering in the new one.

Was this reply helpful? Yes No
Johns222 65 on at

Like (0)

Report

Hi I tried this and no luck

Was this reply helpful? Yes No
Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

What trigger are you using? Are the two environments in the same M365 tenant?

Was this reply helpful? Yes No
Johns222 65 on at

Like (0)

Report

Yes they are in the same tenant and I am using 'When a row is added, modified or deleted' action in the beginning. A powerapp manually begins the process.
Here is an error message that appeared -

Was this reply helpful? Yes No
Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

If you are calling the flow from a Power App then you need to remove the flow in the Power App and re-add it to re-establish the link to the flow. Be sure to copy the formula first and put it in a notepad because removing and re-adding the flow will reset the command line to a bare .run( command.

Was this reply helpful? Yes No
Johns222 65 on at

Like (0)

Report

Hi @Pstork1
Thanks for your help.
I go to Action and power automate in the powerapp but cannot see any flows here. Same with the dev environment. Is it possible to have no flows listed in the powerapp but the flow still be triggered upon clicking a button in the powerapp?

If you are wondering, I was not the one working on this app from the ground up.

Was this reply helpful? Yes No
Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

The ability to see a flow and add it to a button in Power Apps is dependent on the trigger in the flow. It has to be a Power Apps manual trigger. If any other automated, recurrence, or manual trigger is used it will not be visible in Power Apps and you won't be able to call it from a button. The one exception to that would be the When an HTTP request is received. But that is going to generate a URL that is specific to the environment and flow where it was created. So trying to copy that flow and re-use it will break any connection. That is also an older configuration and really doesn't need to be used anymore.

Solutions can also cause issues in this scenario. Were the Power App and Flow both created in a solution and moved into the new environment that way? If they are created first and imported into the solution that can cause an issue after moving them.

Was this reply helpful? Yes No
Johns222 65 on at

Like (0)

Report

Hi @Pstork1

Yes exactly, this was all created in solutions and imported into the user environment using solutions. Could this be why I am facing issues now? Thanks

Edit: Sorry to add onto that, the flow was definitely created in a solution, and the powerapp was created in 'apps'. The powerapp also has a solution. Would that mean I need to re-create the flow? Thanks again

Was this reply helpful? Yes No
Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (1)

Report

If the Power App calls the flow then they need to have been created in the same solution. If they are moved to another environment in separate solutions then you will have exactly the kind of issues you are having. In general there is no easy way to fix that and the normal fix usually involves rebuilding everything from scratch.

Was this reply helpful? Yes No
Johns222 65 on at

Like (0)

Report

Thank you, this was the issue in the end. They were in different solutions and I didnt know they had to be the same.

Was this reply helpful? Yes No