Unanswered

Triggering multiple instances of the same flow simultaneously?

(0) Share

Report

Posted on by jpirelli Microsoft Employee

Yesterday I was testing my BOT which calls a flow to create an ICM ticket. In doing so, I ran into an unexpected, and untrapped error in the dialogue JSON which really threw me for a bit of a loop. Basically, due to a wait step in my process, I had attempted to trigger the flow again before the previous run had completed. I wasn't aware that you could only instantiate a single flow at a time and I was curious if there is a way around that particular restriction or do I need to get a bit more creative with my solution to reduce the chance of collision?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Dhinakaran 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @jpirelli

Please try the below steps and see if it resolves for you.

1. Go to Settings of the first Flow Step.
2. Turn on the Concurrency control and set the Degree of Parallelism to 1.
I have attached an image for you reference.

Hope it works!.

Best,
Dhina

Was this reply helpful? Yes No
JoeGill 175 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi Dhina,

Happy to be wrong on this. If you change the degree of Parallelism to 1 then you need to change your Flow to be asynchronous. I could not get my Bot to call an Asynch Flow. I would have been surprised if it did as it would require a callback of some type from Flow to PVA.

I was able to add a 10 delay to my flow and call it from multiple Bot sessions without any problem.

Joe

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

Like
a
(0)

Report
Copy link

Link copied!

I did a bit more testing, by default, flows can run concurrently. This is great info but maybe a red herring on my errors last night. I was able to reconfirm that multiple instance are able to run at once.

I'll keep working on my repro, this could have been a red herring entirely.

Was this reply helpful? Yes No
Dhinakaran 31 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi JoeGill,

You are right. This makes it want to run as asynchronous, so we are pretty much not able to leverage the concurrency control feature as we typically use "Response" action as part of Power Automate with PVA.
Thanks for pointing out, JoeGill 🙂

Best,
Dhina

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

Like
a
(0)

Report
Copy link

Link copied!

Your should be able to trigger the several instances of the same flow to run at the same time from PVA, this is supported.

Was this reply helpful? Yes No