There is a problem with the flow's trigger. InvokerConnectionOverrideFailed.

[stapes]

I know this is a known issue, but how long is it going to be a problem.

InvokerConnectionOverrideFailed. Failed to parse invoker connections from trigger 'manual' outputs. Exception: Could not find any valid connection for connection reference name 'shared_sql_1' in APIM tokens header.

We have Apps that have long been deployed, that are now starting to fail with this for no good reason.

The problem is that the users do not realize a Flow has failed, unless it is obvious.

The solution offered - to delete the flow & rebuild - is impractical, given the large number of complex flows we have.

[CFernandes]

@stapes 

What is the Trigger action, that you are using? Perhaps you an share a screenshot of your solution.

[stapes]

@CFernandes 

This isn't one flow. This is all of them.

The flows were previously working.

[CFernandes]

@stapes 

The problem is most likely caused by the Trigger (usually PowerApps). You will need to disconnect and reconnect the trigger for everything to start working again.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

@CFernandes  I don't know how to do that. May be relevant, but I just checked the Gateway, and see this message: 

Online | A new version of this gateway is available. Get it now.

[CFernandes]

@stapes  You need to do this very carefully. In youe Power Apps you will need to remove the connection and re-add it. 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

@CFernandes I do not know how to do this. Tried deleting and recreating the trigger, but this did not work. The only thing that does work is to delete the flow & rebuild from scratch, but this is completely unacceptable given the number of complex flows we have.

[CFernandes]

@stapes Export and Import the Flow? Does that work? https://flow.microsoft.com/en-us/blog/import-export-bap-packages/ 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

@CFernandes 

These triggers were created when the Flows were created using the method below:

[CFernandes]

@stapes 

I understand you problem and we have completed all the basic troubleshooting

• Reconnecting the Flow in Power Apps.
• Import\Export the Power Automate.

and it seems we are still not getting to a resolution and the only solution would be rebuilding the Flow(which I think is not a solution - waste of time\resources). 

You also mentioned nothing was changed in your environment and the Triggers are just breaking. I would request you to open a Ticket with Power Automate support. https://admin.powerplatform.microsoft.com/support 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

@CFernandes 

Exporting the Flow and Importing it works. 

I have so far imported ten of the flows used by the app. Then I have to edit the App to replace the old version of each flow with the new one. Long winded, but it seems like the only way I am going to get my App working again soon.

Thanks for trying. I don't see any way to remove the PowerApps trigger & add a new one in the App editor, unless it is one of these:

I will try to raise an issue as you suggest.

[CFernandes · Accepted solution]

@stapes 

Hey Mate, You only need to remove the Flow associated in our Power App and re-add. (You do not need to remove the trigger).

You can have a look at my video(1:06 minutes) https://www.youtube.com/watch?v=tStHVc4uKNI  (give that a try).

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[stapes]

Thanks @CFernandes 

I know how to do that. In fact I had to do that for every single flow after the import.

This is much worse than you think.

One flow I repaired & got working in the App is broken again already!

What is causing this?

We cannot possibly be expected to delete & re-add every flow every day.

Update:

This turned out to be the result of a bad parameter being sent, so it is a misleading error message. We should close this thread. Thanks for your help.

[stapes]

@CFernandes 

Turns out deleting the Flow from the App & Re-adding it works. That will save some time. Thanks.

[CFernandes]

Hey @stapes , I am glad that your problem has been resolved. 🙂 I am glad the video helped. 

[sastrakhan]

In my case I had to just "test" the flow and it prompted me to reinsert my credentials for the missing permissions and then it worked. 

[datey8819]

Issue fixed after removing the flow from custom page [Power App Triggered] and added it again.

Thanks

[RoarkeP]

Hey all,
My issue was related to deploying a managed solution into test/prod environments. When I would import the solution with 5 flows and a canvas app into production, the flow connection references would not update. Users were getting:

What ended up fixing the issue was quite simple and easy - did not create any unmanaged layers or require "deleting" and re-adding anything other than the "Run only users" in the Flow Details Screen. I removed the users group, re-added them and selected the connection I wanted to point them to for all five flows and it resolved the issues.