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?
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.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.