Unanswered

Manually triggered flow: "there's a problem with the flow's trigger"

(0) Share

Report

Posted on by bentoro

An error suddenly appeared whenever a button in a Canvas Power App triggers a flow that I have made.

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

The trigger had been working fine for months and suddenly this error has appeared. I have tried duplicating the flow and updating the Power App, and then it works temporarily. When I log out and log in again, it no longer works.

Could someone explain how to fix this issue? Screenshot 2020-11-07 161753.png

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (0)

Jcook 7,781 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hello @bentoro

You are going to want to remove the flow from the power app. And than re add the flow again.

Was this reply helpful? Yes No
Brad_Groux 4,556 on at

Like (0)

Report
Copy link

Link copied!

Verify that your SharePoint online connection is still logged in and valid via the Data > Connections menu:

Check our SharePoint connector(s) are Connected:

Even if it is Connected, it may be worth refreshing it.

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE. Want to know more? Follow @BradGroux on Twitter, and check out my Medium blog at https://msft.engineer.

Was this reply helpful? Yes No
Hudson Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hey @bentoro ,

Hope you are doing well.

When a flow is added to a PowerApps, the connections that the flow uses are remembered by the PowerApps. If the flow is later updated to have more connections, the PowerApps does not know about it and doesn’t send all the connections that we need.

Try to remove the flow from the PowerApps, saving the app, closing the app, reopening the app( preferably in a new tab), re-adding the flow and resaving to make PowerApps notice the new connections and check if it works?

This is our official documentation about best practices to updating a flow used by a PowerApps for your reference:
https://support.microsoft.com/en-us/help/4477072/best-practices-updating-a-flow-used-by-a-powerapp

Thanks,

Hudson

Was this reply helpful? Yes No
bentoro 6 on at

Like (0)

Report
Copy link

Link copied!

Hello @Jcook,

Thanks for your reply.

I have tried this approach and it does work temporarily, but upon logging out and logging on, or publishing the changes, it breaks again with the same error.

Was this reply helpful? Yes No
bentoro 6 on at

Like (1)

Report
Copy link

Link copied!

Hello @Hudson,

Thanks for your reply.

Unfortunately, this only produces the temporary fix I described previously. I tried following your exact steps and, while it does seem to work to begin with, I tried again this morning and the same error described in my post has come up again.

I think it may have something to do with me publishing the Power App but I am not entirely sure.

Should I consider duplicating the current (canvas) Power App?

Was this reply helpful? Yes No
DroningOn 45 on at

Like (0)

Report
Copy link

Link copied!

I'm also dealing with this error and it is incredibly frustrating, especially because the "flow" I'm using has an approval stage in it. How is this not being considered a bug by the Microsoft Team?

Was this reply helpful? Yes No
Mx81 860 on at

Like (0)

Report
Copy link

Link copied!

I had the same problem.
Solution for myself: I removed the flow in my app and added it again. Now it works fine again.

Was this reply helpful? Yes No