Flow designer Flow does not transferred correctly via Update SetIssue When deleting SubFlows form flow and capturing it into update set, Flow is still having old Subflow attached when committing update set to another instance.Steps to reproduce:1. Open any flow which is having Subflow activity[NOTE: Flow should be the same in both instance/ it should present in bot instances]2. Remove subflow from flow and save it [This should add this flow to the UpdatSet]3. Process and complete update set4. On another instance, capture and commit UpdateSet5. Check moved flow in flow designer[UpdateSet will not remove Subflow activity which you've already removed in base/parent instance]CauseThis is know issue and reported in PRB1527360.https://support.servicenow.com/nav_to.do?uri=problem.do?sys_id=4aaf801f1bbafcd0179233bc1d4bcb56This problem is fixed in San Diego release.ResolutionThis issue occurs because If you delete every single component instance of a type on a flow the cleanup doesn't get put into the update set. --There are 2 work arounds for this issue: 1. do not remove all subflows from a flow on the dev instance. 2. run the following script that will remove all the subflows from the flow. ********************************** function cleanUpSubflowInstances(flowId) { var flow = new GlideRecord("sys_hub_flow"); if (!flow.get(flowId)) { return; } deleteSubflowInstances(flowId); deleteSubflowInstances(flow.master_snapshot); } function deleteSubflowInstances(flowId) { if (!flowId) return; var subflowInstances = new GlideRecord("sys_hub_sub_flow_instance"); subflowInstances.addQuery("flow", flowId); subflowInstances.query(); while (subflowInstances.next()){ subflowInstances.deleteRecord(); } ********************************** This script will remove all subflows within the flow. Moving flows through the app repository or update set are both fine. they should work the same way.