Unanswered

Sharepoint list item updated multiple times in a short period

(0) Share

Report

Posted on by pbernardes

In my process I have to update a sharepoint list item 3 times in a period of 30-45 seconds. I have a Flow configured to run when an item in this list is updated, that should run for all 3 updates but instead is runnig only after the third. Is this an issue or by design?

Categories:

Using flows

I have the same question (0)

All responses (14)

Answers (0)

RobElliott 10,397 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@pbernardesI think that's by design, but try putting in a delay schedule in your flow of perhaps 1 minute before the actions that are supposed to be taken and see if that helps.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

Was this reply helpful? Yes No
yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @pbernardes ,

You can set a concurrency control setting to enable and the degree of parallelism to address this issue. Please refer to the screenshot below:
If you have other workflows creating/ modifying a number of items at once, the flow will be fired in parallel. Settings can be cahnged by clicking the ... on the trigger. Note: once concurrency control is enabled it cannot be disabled.

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
pbernardes 50 on at

Like (0)

Report
Copy link

Link copied!

I am afraid it won't work since the problem is that the flow was not even triggered in the 2 first updates.

Was this reply helpful? Yes No
pbernardes 50 on at

Like (0)

Report
Copy link

Link copied!

Hi @yashag2255 , since the 3 updates are in the same item, it looks that there is no issue with paralellism. It looks to mee that the process that trigger the flow, just take the last change in the item from time to time, instead of creating a queue with all changes.

Was this reply helpful? Yes No
yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @pbernardes ,

Are you talking about 3 changes in a particuar item? (As and when you hit the save button, the flow will be triggered. So even on the same item if you make 3 changes and hit the save button every time it will work as expected)

If you are talking about updating 3 diferent items at the same time (not possible manually but through a workflow), it will trigger the changes in parallel (on the concurrency enabled. also, the trigger will not wait for the current running flow to complete before starting a new one in this case)

Hope this Helps!

Thanks

Was this reply helpful? Yes No
ScottShearer 25,280 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@pbernardes

Can you post a screen shot of your Flow? It is possible that a redesign might solve your issue.

Was this reply helpful? Yes No
pbernardes 50 on at

Like (0)

Report
Copy link

Link copied!

@yashag2255 ,

3 changes in a particular item but all of them done automatically by other flows triggered by the user in SEQUENCE (interval of 15 seconds bettwen them) from an external system.

Was this reply helpful? Yes No
yashag2255 24,769 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hi @pbernardes ,

In that case the flow will be triggered 3 times (one at every 15 seconds). Is it not working that way for you?

Edit: Once Concurrency is enabled, it will trigger a flow every 15 seconds irrespective of the any previous flows status.

Thanks,

Was this reply helpful? Yes No
pbernardes 50 on at

Like (0)

Report
Copy link

Link copied!

Hi @ScottShearer ,

I am pretty sure that the issu is not in the Flow but in the logic that trigger the flow. The flow should have been triggered 3 times but was only one time.

Was this reply helpful? Yes No
pbernardes 50 on at

Like (0)

Report
Copy link

Link copied!

@yashag2255 ,

did not triggered 3 times. Only one just for the last change. I though that turning on the concurrency control I would be limiting the number of trails in parallel. Am I wrong?

Was this reply helpful? Yes No