# Review changes and retire a journey Correcting content, stopping access and permanent deletion are different actions. Confirm the goal before changing learner access. ## Before you begin You have journey-management access and know whether the journey is Draft, Active or Archived. **Worked example** When an old support process is retired, archive its journey to stop offering it. For a typo, edit the existing journey rather than using Archive as a save action. 1. 01 ## Inspect who changed what and when 1. Open Change history in the editor. Inspect time, actor, operation and before/after content, distinguishing unpublished changes from published versions. **Why this matters**Current settings alone do not reconstruct the version a learner encountered. **Check the result**You can locate the relevant change and version rather than relying on memory. Not the expected result? If an actor name or evidence is unavailable, preserve the identifiers and time for investigation rather than filling in a guess. 2. 02 ## Stop offering an active journey 1. In Journey management locate the correct active journey and choose Archive, then read the confirmation. The action is also available in Journey settings. Confirm you are not stopping training that is still needed. **Why this matters**Archiving stops learner access while retaining history. It is not a new publication or a freely reversible pause switch. **Check the result**The journey appears under the Archived filter. Not the expected result? Do not assume an unarchive action exists. Confirm how to provide training again; deletion is not recovery. 3. 03 ## Permanently delete only an unwanted draft 1. Filter to Draft, verify the journey name, choose Delete and read the permanent-deletion confirmation. Keeping an unpublished draft is also an option. **Why this matters**Active journeys do not use the same deletion workflow. Retaining evidence and stopping use are separate concerns. **Check the result**The deletion target is a genuinely unwanted draft, not a version learners have used. Not the expected result? When retention is uncertain, do not delete. Confirm with the training owner first. ## What completion looks like You can inspect before/after changes and use archiving, not destructive deletion, to stop offering a live journey. This preserved change-history illustration uses example names and times. The actual entry is Change history in the journey editor.