I just built a flow that will create a new entry in a second SharePoint list every time an entry in the first list was modified. A new version in the history will be created for every single change.
My problem is that if I'm making two changes in a short period of time the flow will only react to the first one and the second change just will be ignored. The second one isn't listed in the history of the flow, so he doesn't "found" the second change. Does anyone have an idea why that is and how I can change that? It is very important that every change will create a new entry in the second list.
Thank you everybody! 🙂
Flow should be started for both update events. Could you share a screenshot of your flow just in case there's a condition preventing to run the second one?
There is a condition, but even when the condition won't apply, it should be in the history of the flow (but it isn't). So this shouldn't be the issue here. It's like the second change in the list never happended.
Thank you! 🙂
@fchopoaye ... I was thinking that a condition inside the flow itself wouldn't prevent concurrency on other new or modified items.
However, @FelixMbus , Ferran may have been referring to a 'Trigger condition'. Could you click on the "..." menu of the flow trigger and post a screenshot of the settings, please?