Page Comparison

...

• Org: dev

• Task name: batch

• Snaplex details:

  • Name:dev1devplex

  • Location: sidekick

  • Environment:cluster

...

• Org: prod

• Task name: batch

• Snaplex details:

  • Name: prod2 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/sidekick/windowscluster/batch is replaced with the task runtime_path_id of /prod/rt/sidekick/windowscluster/batch.

Example 2

Source Org

• Org:dev

• Task name: batch

• Snaplex details:

  • Name: plexprime

  • Location: cloud sidekick

  • Environment: us-east folio

Destination Org

• Org: prod

• Task name: batch

• Snaplex details:

  • Name: plexprime

  • Location: cloud

  • Environment: us-west

...

• • east

In this case, the Snaplexes in each Org have the same name (in this case, mainplex), the task with the runtime_path_id of /dev/rt/cloud/plexprime/batch from dev Org that is replaced with /prod/rt/cloud/plexprime/batch in prod Org does not work- 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.