Flow designer is not working properly after moved by Update SetSummaryThere are cases where flow is not working when moving via update set from instance to instance. such as Flow running with error, action is been executed properly, flow can't be open, etc. It may due to various reasons. As flow contains many detailed records such as "sys_hub_flow_base, sys_hub_flow" sys_hub_flow_snapshot is when the flow has been compiled it will be generated with the latest snapshot.InstructionsSince moving a flow should ideally generate all required records in the update set, including its subflow and actions. Current, flow, and UpdateSet are separate functions and UpdateSet is not checking the flow and its subsequent record's consistency. if the flow been moved is not working as expected it is always better to try the followings it may solve the problem. 1. Make a small change (eg. Edit an annotation) and re-activate the flow.2. How to re-compile flows and actions without modifying their contents3. re-publish flow and action to avoid any missing record like sys_complex_object if all doesn't work, then raise a case and contact support.Related Linkssys_hub_flow_snapshot only holds non-update-to-date flow information. That's why it's named 'snapshot' and the table has updateSync=false sys_hub_flow holds the published flow information. It will be captured by Update Sets.