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

• Org: dev

• Task name: batch

• Snaplex details:

  • Name:dev1

  • Location: sidekick

  • Environment: windowscluster

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/sidekick/windows/batch is replaced with the runtime_path_id of /prod/rt/cloud/k8/batch.

Example 2

Source Org

• Org:dev

• Task name: batch

• Snaplex details:

  • Name: mainplex plexprime

  • Location: cloud

  • Environment: aws us-east

Destination Org

• Org: prod

• Task name: batch

• Snaplex details:

  • Name: mainplex plexprime

  • Location: cloud

  • Environment: aws us-west

However, in the case where the Snaplexes in each Org have the same name (in this case, mainplex), the task with the runtime_path_idsid of /dev/rt/clousdcloud/mainplex/testtask1 and plexprime/batch from dev Org that is replaced with /prod/rt/clouscloud/mainplex/testtask2plexprime/batch in prod Org does not work.