...
When a task is migrated to another Org, the Snaplex references are set by the runtime_path_id property and not by the Snaplex name. Accordingly, you should make sure that the values for the Location and Environment fields in the Snaplex dialogs match - not the Name field, as might be assumed.
...
Example 1
Source Org in migration operation.
Org: dev
Task name: batch
Snaplex
...
details:
Name: dev1
Location: sidekick
Environment: windows
Destination Org
Org: prod
Task name: batch
Snaplex details:
Name: prod2
Location:
...
cloud
Environment:
...
k8
When migrating the task batch from the dev to prod Orgs, a task from the dev Org with the runtime_path_id of /dev/rt/cloudsidekick/westwindows/batch is replaced with the runtime_path_id of /prod/rt/cloud/testtask, even if the two Snaplexes have different name labels, such as devplex and prodplex.However, the task with the associated Snaplexes that are both labeled mainplex in each Org, with /k8/batch.
Example 2
Source Org
Org: dev
Task name: batch
Snaplex details:
Name: mainplex
Location: cloud
Environment: aws-east
Destination Org
Org: prod
Task name: batch
Snaplex details:
Name: mainplex
Location: cloud
Environment: aws-west
However, in the case where the Snaplexes in each Org have the name mainplex, the task with the runtime_path_ids of /dev/rt/batchclousd/mainplex/testtasktesttask1 and /prod/rt/otlpclous/mainplex/testtasktesttask2 does not work.