What are the each option will do when Trigger is Updated in Flow Designer?

[RajeshEdaguttu]

Hi All,

What will do each option in Run Trigger when trigger is Updated in Flow designer? Please explain with an example and also please share any documents if you guys have?

Regards,
Rajesh Edaguttu.

[Dr Atul G- LNG · Accepted solution]

Hi @RajeshEdaguttu 

https://www.servicenow.com/docs/r/washingtondc/build-workflows/flow-triggers.html

Trigger	Description
Created	Starts a flow when a record is created in a specific table.
Updated	Starts a flow when a record is updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow.
Created or Updated	Starts a flow when a record is either created or updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow.

[Dr Atul G- LNG · Accepted solution]

Hi @RajeshEdaguttu 

https://www.servicenow.com/docs/r/washingtondc/build-workflows/flow-triggers.html

Trigger	Description
Created	Starts a flow when a record is created in a specific table.
Updated	Starts a flow when a record is updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow.
Created or Updated	Starts a flow when a record is either created or updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow.

[RajeshEdaguttu]

Hi @Dr. Atul G,

Thank you for explanation and document. 

[Tanushree Maiti · Accepted solution]

Hi @RajeshEdaguttu 

Refer: https://www.servicenow.com/docs/r/build-workflows/workflow-studio/flow-triggers.html

Trigger Description

Created	Starts a flow when a record is created in a specific table.
Updated	Starts a flow when a record is updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow.
Created or Updated	Starts a flow when a record is either created or updated in a specific table. Requires selecting when to run the flow. For each unique change: Triggers the flow for every unique update to a non-system field even if the flow is currently running. Note: The system stores a history of every change to a record and determines whether the change is unique. For example, if an incident record's State field changes from In Progress to On Hold, the flow can run. However, if the State field then changes back to In Progress, the flow can't run. Note: Flows that have a record trigger that runs For each unique change can produce recursions when run in a non-interactive session. When this type of flow makes a change to the trigger record, the change meets the flow trigger conditions and causes a recursion. Once: Triggers the flow once for the life of the record. Only if not currently running: Triggers the flow for every unique record change if the flow is not currently running on this record. This behavior is the same as the Always option in previous releases. For every update: Triggers the flow every time that the record is updated, regardless of whether there has already been or currently are any running contexts for the flow

[RajeshEdaguttu]

Hi @Tanushree Maiti ,

Thank you for explanation.