Hi,
I want to know about flow designer concept.
Can anyone please tell about Run Trigger options like Once, For each unique change, Only if not currently running, For every update. When we should use this.
Regards,
Nivedita
Hello @niveditakumari,
the 4 different trigger types for the Update trigger can be described as following:
- For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. For example, if an incident record's State field changes from In Progress to On Hold, the flow will run. However, if the State field then changes back to In Progress, the flow wont be triggered.
- Only if not currently running: Triggers the flow for every unique change if the flow is not currently running. Basically the same as the previous one, but it avoids that the same flow is running twice at the same time. For example if multiple updates to the record are made really quickly it could happen that the flow was triggered by the first update and is still running when the flow is triggered again by the next update. if you want to avoid this, chose this option instead of the first.
- For every update: Triggers the flow every time the record is updated, regardless of whether the same flow is already running or this update has already been made in the past.
- Once: Triggers the flow once for the life of the record. Only on the first update the flow runs and then never again
In general you can say that the different trigger types "contain each other". So the "once" trigger type is triggered only in a very special case. Then the "Only if not currently running" is triggered in more cases, while the "For each unique change" even in more cases etc.
The two extremes would be "once" vs "for every update"
I would suggest trying them all out on a PDI to get a general feeling and then decide based on your requirements.
I hope this helped. If yes, I would appreciate if you could mark this answer as "correct solution". Thank you!
Greetings,
Sören
Hello @niveditakumari,
the 4 different trigger types for the Update trigger can be described as following:
- For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. For example, if an incident record's State field changes from In Progress to On Hold, the flow will run. However, if the State field then changes back to In Progress, the flow wont be triggered.
- Only if not currently running: Triggers the flow for every unique change if the flow is not currently running. Basically the same as the previous one, but it avoids that the same flow is running twice at the same time. For example if multiple updates to the record are made really quickly it could happen that the flow was triggered by the first update and is still running when the flow is triggered again by the next update. if you want to avoid this, chose this option instead of the first.
- For every update: Triggers the flow every time the record is updated, regardless of whether the same flow is already running or this update has already been made in the past.
- Once: Triggers the flow once for the life of the record. Only on the first update the flow runs and then never again
In general you can say that the different trigger types "contain each other". So the "once" trigger type is triggered only in a very special case. Then the "Only if not currently running" is triggered in more cases, while the "For each unique change" even in more cases etc.
The two extremes would be "once" vs "for every update"
I would suggest trying them all out on a PDI to get a general feeling and then decide based on your requirements.
I hope this helped. If yes, I would appreciate if you could mark this answer as "correct solution". Thank you!
Greetings,
Sören
