Workflow does not open in workflow editor after migrating from one instance to anotherIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> A workflow is created in the source instance, exported, and then imported on the target instance. This is done using the steps mentioned in the documentation page below: Workflow movement with update sets However, when trying the open the workflow on the target instance, the workflow editor may seem to be loading indefinitely. CauseOne of the reasons for this is that one of the wf_acitivity in the wf_workflow_version, may be referring to a non-existing wf_element_definition. The table [wf_element_definition] is the parent for both wf_activity_definition (Normal Workflow Activities) and wf_element_activity (Orchestration activities). Whereas, workflow export handles the wf_acitivity records, and wf_element_definition are not included in the update set automatically. Hence, in case the activity has been customized and a new sys_id has been generated, it must be captured in the update set.ResolutionThe resolution is to migrate the custom activity definition to the target instance. Break-Fix: Review the Workflow Activities related list of the broken wf_workflow_version record.For each of the workflow activity where you see or suspect a blank display value, note down the sys_id.Search the sys_id noted in Step 2, in the wf_element_definition table on the target instance to ensure that the records are missing (if not, this may be a different issue).Login to the source instance and export the relevant wf_element_definition records in an update set.Retrieve the update set created in Step 4, to the target instance. Process change (to avoid future issues): Make sure to capture the customization made to 'Activity Definition' in and update set and transfer them to other instances.Each time a workflow is transferred from one instance to another, it must be ensured that the custom activities definition related to it are already present on the target instance.Related LinksKB0541991- Workflow resources Page KB0549843 - Workflow troubleshooting - Unable to create or open a Workflow Version [wf_workflow_version] record