Page Comparison

...

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:devplex

  • Location: sidekick

  • Environment:cluster

Destination Org

• Org: prod

• Task name: batch

• Snaplex details:

  • Name:

...

• • prodplex

  • Location:

...

• • sidekick

  • Environment:

...

• • cluster

When migrating the task batch from the Org dev to the Org prod Orgs, a task from the dev Org with the the task runtime_path_id of /dev/rt/cloudsidekick/westcluster/batch is replaced with the task runtime_path_id of /prod/rt/sidekick/cluster/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 runtime_path_ids of /dev/rt/batch/testtask and /prod/rt/otlp/testtask does not workbatch.

Example 2

Source Org

• Org:dev

• Task name: batch

• Snaplex details:

  • Name: plexprime

  • Location: sidekick

  • Environment: folio

Destination Org

• Org: prod

• Task name: batch

• Snaplex details:

  • Name: plexprime

  • Location: cloud

  • Environment: east

In this case, the Snaplexes in each Org have the same name - not the same Location and Environment values. Therefore, when migrating the task batch from the Org dev to the Org prod, the Snaplexes are not automatically mapped, and you need to select the Snaplex manually in the settings dialog for each task.