My BOT is scheduled to run every 30 min.
My cloud flow which is scheduled calls a desktop flow. Some times, when the data is huge, Desktop flow runs for more than 4 hours. So, the next subsequent schedule/session gets queued up. How to avoid this?
Is there a way to check if the Virtual Machine is free before calling a desktop flow?
I would solve this by adding Concurrency control to your Cloud flows trigger. Set it to 1 so that one cloud flow can be running at a time.
So in your Recurrence -trigger go to Settings and under General > Concurrecy control set it to 1
Then the flow does not start if there is another flow still running. Example: If your flow is set to trigger every 30minutes and one starts at 10:00 and it runs for 1h20min then the next time your cloud flow will start is 11:30.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
9
Share
Report
All responses (
Answers (
