Archive a workflow
Retire a workflow that's no longer used so no new instances start, without losing its history.
On this page
Archive a workflow when the process changed completely or is no longer used. Archiving doesn't delete anything: existing instances are kept and running ones finish normally.
Before you start
You need Administer in Workflows.
If it's a catalog workflow, check which items use it: after you archive it, those requests are created without a workflow.
Archiving can't be undone from the screen.
Steps
Go to Workflows → Definitions.
On the workflow's row, press Archive.
Read the confirmation Archive "…"?:
if it has no active instances: "No new instances will start. The history is kept.";
if it does: "It has N running instance(s): they continue until they finish, but no new ones start."
Press Archive.
You'll see Workflow archived.
What happens next
The workflow disappears from Definitions and can no longer be opened in the modeler.
No new instances start: not manually, not from catalog requests, not from changes.
Its published version becomes retired and no longer counts toward your plan's maximum of published workflows.
Running instances continue until they finish, and their tasks and approvals stay in My tasks.
All its instances, including finished ones, stay in Workflows → Instances with their history.
The key stays taken: a new workflow needs another key.
If you only want to change how the process works, don't archive it: edit it and publish a new version. Running instances keep their version and new ones use the new one. See Validate and publish a workflow.
If you archive the CAB approval workflow, normal or emergency changes that move to assessment will no longer have automatic approval. Publish the replacement workflow first.