Flow triggered twice, which also created duplicate catalog tasks.Issue Flow triggered twice, which also created duplicate catalog tasks.ReleaseOrlandoCauseThe issue started even before the flow got triggered. if we check the audit, the system updated the approval twice on the request, Because the approval is updated twice, "Start FlowDesigner Flow" business rule condition matches twice and hence two flow contexts are seen. This usually happens if there there is a customized before business rule on sc_req_item table that is updating the request when the RITM record is inserted. ResolutionPlease create the business rule directly on request table, insert, run it "after" and give higher order to fix this issue.