Flow designer - duplicate state changes in same transaction, triggering BRs twiceDescriptionThe flow runs on RITM, and once approved, it generates a sc_task for the business to get on with.The flow waits for that to complete, and then updates the RITM to be closed.The closure of any RITM triggers a business rule to have an audit of that request against the raiser.(BR "RITM Closure Mandatory Actions");However we've (customer) noticed that in some cases, the business rule runs twice, causing misleading duplicate updates to the State field.Release or EnvironmentnaCauseWe checked and confirmed that the custom business rule was not being triggered twice and is not related to the cause. There were 2 audit entries for State change to Closed even when the custom business rule was skipped. We reviewed the example provided: https://instance_name.service-now.com/nav_to.do?uri=sc_req_item.do?sys_id=b68d96e21bc159d042a2ec6fe54bcb08 Checked the Flow context: https://instance_name.service-now.com/$flow-designer.do#/operations/context/8f8d96e20ac159d059fa149136a46c45 What is happening: 1. When the catalog task is closed, the flow execution sets the *Stage* to Completed and *State* value to Closed Complete on **Update Record** action. 2. This triggers the OOB **Set Active Flag** business rule to update the **Active** field to false. 3. Then, we have another OOB business rule **task closer** which triggers and updates the **State** value to **Closed Complete** within the same transaction: https://instance_name.service-now.com/nav_to.do?uri=sys_script.do?sys_id=475ef3c5c611228401440a7a5f29a786 Conclusion: The State field is being updated once by the flow action and then another time by the OOB business rule.ResolutionRemove the **State** field from **Update Record** flow action as the OOB process will take care of it anyways.