I rediscovered what@Shikkou pointed out, and the solution worked for me. I will elaborate the action step, as it's not super clear from his answer.   Say your 'Master-Workflow' looks like this,  START Fork-1 Sub-Workflow-1-0 Sub-Workflow-1-1 Fork-2 Sub-Workflow-2 END   When you export this workflow, the exported json file, Master-Workflow.json might end up looking like [ { .... "name": "SUB-WORKFLOW-1-0" }, { .... "name": "MASTER-WORKFLOW" } { .... "name": "SUB-WORKFLOW-2" }, { .... "name": "SUB-WORKFLOW-1-1" }, ] If Sub-Workflow-2 lists either of Sub-Workflow-1-0 or Sub-Workflow-1-1 as a dependency, it will throw the error OP mentions.   The solution is to simply edit 'Master-Workflow.json' to reflect the correct order, which in this case looks like [ { .... "name": "SUB-WORKFLOW-1-0" }, { .... "name": "SUB-WORKFLOW-1-1" }, { .... "name": "SUB-WORKFLOW-2" }, { .... "name": "MASTER-WORKFLOW" } ]   You should now be able to import the entire thing!   P.S. - Unlike what @Adlin has pointed out, we were able to import entire workflows between users on different clusters without making any of the changes he has listed. ... View more