Roll Back a Workflow v2

Roll back by restoring an earlier design as a new latest revision. This preserves the audit trail and lets you validate old content against current dependencies before it is promoted.

Restore and test the revision

  1. Open the Workflow designer in the first-ranked Test Environment.
  2. Open Manage revisions.
  3. Select the earlier revision and review its message, author, time, and content.
  4. Open that revision in the designer.
  5. Confirm its Node versions, Connections, Sub-Workflow contracts, scripts, triggers, and input/output schema are still valid.
  6. Run it in Debug with representative, non-destructive inputs.
  7. Inspect the result, Problems, and logs.

Save the rollback

  1. Click Save.
  2. Enter a message that identifies the restored revision and the reason for rollback.
  3. Confirm that Revision Management shows a new latest revision. The older history is not deleted or rewritten.
  4. Confirm that the Test publish matches the new latest FileHash.

Promote and verify

When Release Management is enabled:

  1. Open Manage releases.
  2. Promote the restored revision through each Environment in rank order.
  3. Wait for each target to show the expected published revision.
  4. Review Workflow Status separately and enable the Workflow where required.
  5. Run a safe verification through the target Environment's actual interface.

When Release Management is disabled, the save publishes the shared source across the Site Environments. Verify the active revision and status in each Environment that matters.

If the earlier design no longer compiles, do not bypass the failure. Repair the compatibility issue in the restored design, test it, and save that corrected content as the rollback revision.

See also

See Revisions and Releases, Revision Management Pane, and Release Management Pane.