web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Concurrency Control tu...
Power Automate
Unanswered

Concurrency Control turned off when cloud flow is published

(4) ShareShare
ReportReport
Posted on by
I'm working with cloud flows within a solution. Recently (last 2 weeks) I have noticed that the Concurrency Control I've turned on for Apply to Each Actions is being turned off when I Publish the flow after making changes. Has anyone else experienced this behavior?his?
Categories:
I have the same question (0)
  • DR-26070948-0 Profile Picture
    3 on at
    I have the same issue. Have you found a solution to this yet?
  • Verified answer
    sigmandel_rimac Profile Picture
    8 on at
    I did some tests and found that it's a web UI issue. The concurrency setting is always shown as "off" only when using the new designer.

    It's actually very severe because you don't need to publish it. If you edit anything (even if you don't edit the for-each step) and save it, it will save the flow with concurrency off! That can be confirmed by refreshing the web page after saving; it will show as "off".

    That's how I found out after making a little change to one of my critical flows just to later discover later that the flow was broken. I tried many things including reimporting the flow from a saved package, yet because I was using the new designer, it kept showing as "off".
     
    To fix:
    1. edit it using the old designer.
    2. turn on concurrency.
    3. save it.
  • bbains Profile Picture
    on at
    sigmandel_rimac's answer identifies and corrects the issue. I'm adding a little for info based on my experience. New designer definitely shows concurrency as "off" when you open a flow and click on a control with the concurrency property. What I have noticed is that I can turn the setting back on, select a different action in the flow, and then save and publish the flow, the concurrency setting gets saved as on. This observation is based on the fact that flow execution time is in line with run times when concurrency is "on" after doing this. 
  • Suggested answer
    CU02081222-1 Profile Picture
    2 on at
    The issue should be fixed and rolled out on 8/9. 

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.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 522 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 364 Moderator

#3
abm abm Profile Picture

abm abm 243 Most Valuable Professional

Last 30 days Overall leaderboard