16 Flow Limit?

[KevinLandt]

Hi there,

I'm using a flow within PVA and am getting the following error:

Request to XRM API failed with error: 'Message: Connection reference 'cr10b_sharedonedriveforbusiness_e5738' is already associated with '16' flows. The limit is '16' flows for performance reasons. Please create a new connection reference to use with this flow. Code: 0x80090444 InnerError: '.

The flow (image here) is designed to grab a thumbnail from OneDrive and then return the URL as a variable. Each flow is NOT running at the same time, so performance shouldn't be an issue. Is there a better way to code this functionality such that I don't run into an arbitrary limit? I read about creating a new connection however I'm unclear on how to accomplish this.

Thanks in advance for any advice!

[Expiscornovus]

Hi @KevinLandt,

That is the connection reference limit you are running into with your OneDrive connection. One connection reference can only used by 16 flows. 

In this Microsoft Doc you can read about this limit and also how you can create a new connection reference for your OneDrive connection:

https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-connection-reference#limits

[KevinLandt]

Thanks so much. I've tried using the suggestions in this document, however when I log in to Power Apps my bot is not present. I originally authored and configured the bot from within Microsoft Teams (under the same account). If I create the Connection there, and my bot isn't showing, will they be able to connect?

Another question. When I went to choose the connection for the reference, I chose OneDrive for Business. Is this correct? Is there a way to link the actual folder or is it making a connection at the account level?

Just as a heads up, my company has set me adrift with this. I have no coding background and am learning as I go. All I want to do is get an image into my bot, and calling an action via Flow was working (until I hit 16). If there is an easier way to get a bot to return an image, please let me know. I've tried almost everything...

Thanks so much for your response!

[Expiscornovus]

Hi @KevinLandt,

I would keep using that OneDrive approach. That's an easy way to store your image.

You can also switch/create the new connection in the settings of an Power Automate action. You can create a new one over there and you can even use the same account as your previous connection.

[KevinLandt]

This is perfect and just what I was looking for. I'll give it a try on Monday 🙂 Cheers, and have a great weekend

[KevinLandt]

Ha! So the latest issue is that I'm trying to add the new connection reference (as you awesomely showed in your screenshot) and it kicks me to an authorization page which just spins... and spins.. and spins...

Is there another way to add the connection reference or do I simply not have this permission in my role?

[KevinLandt]

I am able to add another connection reference back in my Power Apps page, but for some reason while creating my bot in Teams it doesn't view any of the Flows or Connections I have established over there. Like I said earlier, my bot doesn't even show up on the Power Apps page... Do you think there is an information flow issue?

[Expiscornovus]

Hi @KevinLandt,

In regards to that spinning authorization page. Have you tried setting up that new connection from a new in-private tab in your browser? Maybe that helps you to load the authorization page properly?

[KevinLandt]

When I click on the link to create the additional connection (from within Teams), it automatically opens a new tab in the browser. I can't get it to default to an incognito tab. 

I can make the flow I'm looking for in the Power Apps home page, and it's showing up in Power Automate, but I can't select that flow to import into my PVA. 

It still seems like the right hand and left hand don't know each other exist...

[jutrust]

Just in case anyone sees this in 2023 and panics like me: This has been updated. Follow the link and you'll now see "

• Connection references are now saved asynchronously. Unlike during the preview period, there's no longer a limit to how many flows can reference the same connection reference. When connection references are updated, an info banner that links to a panel containing asynchronous update details appears.
• There is also no limit to the number of actions in each flow that can be associated with the connection reference"