Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Update set migration risk

Log in to subscribe to topics and get notified when content changes.

Update set migration risk

Update Set B is migrated and committed to the production instance.

  1. Workflow A - Version 3 is set to unpublished.
  2. Workflow A - Version 1 remains unpublished.
  3. Workflow A - Version 2 is committed and becomes the only published version of the workflow.

    The workflow has gone back a version, perhaps unintentionally. The regressed version becomes the currently published version.