@ServiceNow Use6 ,
Well that depends on business use case but a general idea can be:
1. For every update
When it runs:
The flow runs every time the record is updated, no matter what field changed.
Use case:
When you need the flow to respond to any modification (e.g., logging every change, recalculating a score).
Be careful:
This can trigger very frequently and cause performance issues if not filtered properly.
2. For every unique update
When it runs:
The flow runs only when the values that actually trigger the condition change — i.e., a unique change occurs.
Use case:
When you want to act only once per meaningful change (e.g., status changes from New → In Progress).
If the same value is updated again without a real change, it won’t trigger.
3. Only once
When it runs:
The flow runs just the first time after the record is created or updated to meet the condition, and will not run again even if the record changes later.
Use case:
When you want a one-time action, like sending a welcome notification or initializing a setup task.
4. Only if not currently running
When it runs:
The flow runs on update only if another instance of the same flow is not already running for that record.
Use case:
To prevent multiple concurrent executions for the same record — useful in long-running flows or loops (e.g., task generation or approvals).
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
