Flow Designer contains duplicate state changes in same transaction triggering Business Rules twiceDescriptionThe flow runs on RITM, and once approved, it generates a sc_task for the business to get on with. The flow then 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 ("RITM Closure Mandatory Actions"). In some cases this business rule seeems to run twice, causing misleading duplicate updates to the State field.CauseThere were two audit entries for State change to Closed even when the custom business rule was skipped, and only running when expected. The affected sc_req_item was checked within the Flow Context. When the catalog task was closed, the flow execution set the *Stage* to Completed and *State* value to Closed Complete on **Update Record** action. This triggers the out-of-box 'Set Active Flag' business rule to update the 'Active' field to false. Further, the other out-of-box business rule 'task closer' triggers and updates the 'State' value to 'Closed Complete' within the same transaction ( /nav_to.do?uri=sys_script.do?sys_id=475ef3c5c611228401440a7a5f29a786 ), causing the State field being updated once by the flow action, and then another time by the business rule.ResolutionRemove the 'State' field from the 'Update Record' flow action, as the out-of-the-box process will take care of that.