cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
kbirstein1
Advocate III
Advocate III

Concurrency Control A Good IDea with Large SharePoint List?

I have a flow that can create up to 3,500 SharePoint tasks in one "Apply to Each" (it has to create 7 tasks, Monday through Sunday) for 500 entities).

 

I'm leery of using the Concurrency control since this is a SharePoint Online list and it can take up to 3 minutes to delete 100 items from this large list (it holds up to 950,000 items and there are 15 fields in each item, one of which can be an extensive multi-line notes field). 

 

Does anyone have experience with using Concurrency in an "Apply to each" that can create so many tasks? I'm afraid that hitting the SharePoint list with so many writes at once would make it skip records or hang up. However, it would be nice to make the flow run faster by perhaps setting the concurrency to 10?

concurrency.jpg

 

4 REPLIES 4
sergeluca
MVP

The apply to each is limited to 5000 iterations (100.000 in Flow plan 1)

 

Correct, but that's not what I'm asking. In my Flow, each "Apply to Each" can create up to 3,500 SharePoint items, so the 5,000 limit is not an issue. The issue is:

 

How many "Create Item" commands can a SharePoint list deal with concurrently? 

 

I assume that a SharePoint list can't handle 3,500 simultaneous commands to "Create Item". But is it safe to ask it to create 20 concurrently. Note that the SharePoint list can have as many as 950,000 items in it.

Hi @kbirstein1,

 

Maybe you could take a try to set the concurrency to 10,20,and 50.

 

Best regards,

Alice

takolota
Helper II
Helper II

As of 07/23/2021, I was able to use a SharePoint Create Item action within an Apply to Each running at 13 concurrency within another Apply to Each running at 15 concurrency, so 13 x 15 = 195 Create Item actions at a time.

This could go for a few hours before getting throttled.
I couldn't get it to run anything much higher than this, so I think the concurrent request limit for SharePoint is currently around 200 for a few thousand rows of data. If you want to do more than a few thousand actions, then I suggest drastically reducing the concurrency to achieve about 100 actions per minute or less and using exponential retry policies to avoid being throttled. Plus you may be limited in the number of flow actions per day based on your licenses.

 

Here are more resources about this:

https://support.microsoft.com/en-us/topic/troubleshooting-slow-running-flows-2a51dcd6-0b21-33da-5ce8...

https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations

Helpful resources

Announcements
MPA_User Group Leader_768x460.jpg

Manage your user group events

Check out the News & Announcements to learn more.

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

PowerPlatform 768x460.png

Microsoft Learn

Check out our new Discover Your Career Path blog post series and get all the details.

Users online (1,085)