Opening a subflow throws 'Flow not found' 404 ErrorIssue When trying to open one of the subflow, the user receives a "Flow <sys id> not found" message.ReleaseMadrid patchesCauseFor the subflow which has the issue while opening, there is a nested subflow associated and the mapping for the same is missed in [sys_hub_sub_flow_instance].ResolutionTo fix the instance: Go to /sys_hub_sub_flow_instance_list.do?sysparm_query=subflow=<sys_id_of_the_flow>There should be records associated with the subflowClick into each record (switch scopes if needed to edit these records)Notice the empty subflow fieldSearch for a subflow called and select the top optionSave the record NOTE: This will allow the subflow to open in Flow Designer now. It does look like the inputs to the nested "EM - Base Create Request" subflow have been lost, so these will need to be set again.