Flow gets attached to an existing RITM, if we change the workflow to a flow in the catalog item Issue If we do change a catalog item from a workflow to a flow, requested items created prior to the change with stage "request_approved" will trigger the new Flow in addition to the Workflow previously used as no Flow context exists. Create a new workflow.Publish it with "just begin" and end activities (without any activities being added).Create a new catalog item, and add the above-created workflow to the workflow field.Now save the catalog item.Create a new RITM from the catalog itemMake sure, the workflow is attached to the RITM recordNow go to the catalog item created in step 3. Add the flow "Service Catalog item Request" to the flow field and saveNow go back to the RITM created in step 5.Add comments and click save. ( basically to update something on the RITM)Actual: "Start FlowDesigner Flow" business rule runs and Flow gets attached to the RITMCauseAs the workflow does not update the stage on the RITM record, it will have a value of "request_approved". The stage value matches the conditions defined on the "Start FlowDesigner Flow" business rule (BR), which triggers the flow.ResolutionMake sure whenever a RITM is processed, the end state and stage values are "Complete" and "Closed Complete" (As per Out Of Box) so that the BR does not get triggered.