RELATED IDEAS
Add the ability to "lock" a list item against a workflow so that only one instance can run concurrently
Add the ability to "lock" a list item against a workflow so that only one instance can run concurrently per list item.
If you are running a sharepoint online trigger, this would be a great addition.
At the minute, sharepoint online modified on triggers can fire multiple times, unless you immediately update the item with a field to stop the trigger. This can be problematic when multiple workflows need to be triggered against an item at the same time, as the multiple immediate update item actions will conflict.
If you are running a sharepoint online trigger, this would be a great addition.
At the minute, sharepoint online modified on triggers can fire multiple times, unless you immediately update the item with a field to stop the trigger. This can be problematic when multiple workflows need to be triggered against an item at the same time, as the multiple immediate update item actions will conflict.
-
ADMIN RESPONSESep 7, 2022Connor, thanks for the suggestion - the lock you're describing here already exists and for most scenarios it does not trigger another workflow.
There's a workaround this which is to use separate connections for the start event and action. You'll then need to configure the start event with a condition to filter out on the user used in the action's connection.
If this is still a challenge, please let me know and we can have a chat.
In the future we will look to make distinct connections for start event and actions and by default the start event will filter out events that were triggered by the connection used for actions.
