APIM tokens header Error and Flows Appearing Multiple Times

[stevenpfeifer]

I'm developing a PowerApp that is based on a SharePoint form, and lately when I've created flows to attach the to application they appear in the list of available flows twice.  This is only a recent phenomenon, and does not happen for every flow in that list. 

This is an application that is built as a SharePoint form, but the duplication is happening in Canvas apps as well.

Anyone have a reason that they can see why?  I think that it may be related to the emergence of our flows failing with the error:

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

This error often pops up after making a change to the flow - but note:  changes are not being made to the trigger or output as is noted in this document that MS Support provided me.  The result is that this application has become very fragile to changes involving the flows.

The general "fix" is to remove and add the flow back to the application, but that has ceased to work every time and on multiple occasions I've had to completely tear down and rebuild the flows.

I'm open to any discussion or suggestions for investigation at this point.  We were in the middle of testing this with users and now I'm chasing these things down constantly.

Thanks!

[alrez]

Hi,

Looking at this and other issues that other users have had with this error in the past, I am guessing their is some issue in the connector setting themselves, or something go corrupted. My first recommendation would be to completely delete and recreate the Sharepoint connector in both Power Automate and PowerApps. This will require you to go into each flow and re-point it at the new connections. From there it hard to tell where this should go next. I'd recommend from here trying to see how consistent you can get the issue to reproduce and consider opening a ticket with Microsoft support. I'll include a link below if you would like to go down that path.

If you would like to create a ticket with Microsoft Customer Support here is a link on how to do so: https://docs.microsoft.com/en-us/power-platform/admin/get-help-support

Regards,

Alex

-------

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[stevenpfeifer]

Thank you, We did end up with a Microsoft ticket on this issue, and we haven't gotten an answer back on why we've got multiple flows in each list yet.

As to the APIM token issue, it sounds as if this is a fairly common problem and the tech that we spoke with is hoping that there can be some resolution on it soon.  The recommended workaround of removing the flow from the PowerApp, making the changes and re-adding it to the PowerApp every time that we make a change is cumbersome, so I'm in agreement:  hopefully there can be a fix in place soon so that we don't slow our pace of development.

[jc87]

OMG, I have being going round in circles with this issue for 3 days straight.

It was working on the production environment when I click play, but as soon as I uploaded it and then tried using it from an Iphone I had a connection error and NOTHING I did worked until I tried the following;

• Go to Power Automate and go into the Connections tab under Data. Find the Sharepooint connection and delete it. You will get a warning that you are about to loose connections for the following list of Flows and Apps etc.

• Confirm the deletion.

• Then go to Power Apps and delete the same connection from the Data tab and then delete the connections to the Power Automate Flows.

• Next go back to Power Automate and add a brand new connection to Sharepoint, then go the the flow in question and re-link them to this new connection.

• Go back to Power Apps, reconnect to Sharepoint and then connect the Power Automate Flow from the Action button.

• Then Save and Publish.

• It will then work.

I am guessing that the same process would apply for other data connections, mine was taking and storing photos in Sharepoint.

[stevenpfeifer]

Thanks jc, 

This does fix the issue most of the time.  Once it has been done several times, you can run the risk of it ceasing to work.  At that point, there are 2 options that we were given to try:

1. Remove ALL the connections from the app and re-establish them

2. Build the affected flows from scratch.

It sounds like this is something on MS' Supports Radar.  The only way that we've successfully been able to keep them at bay (thus far) is to make a copy of the flow you are attempting to edit, make the changes in the copy, attach the copy to the app and migrate your formulas to the new flow.  That's what the best practices "workaround" is in the document I linked in the original post.

It is cumbersome to say the least, but we've adopted a best practice naming strategy like BriefFlowFunctionName-vX.x.  That allows us to increment the appended version and make switching the flows in our apps easier.

As far as the flows showing up multiple times when we go to add them.  That is still under investigation.  I'm waiting to close out the topic until I've got that answer so it's documented for other users.