In 30 seconds

Retiring a workflow is real work, not just switching it off. Decide what replaces it, remove its access, preserve what matters, and tell the people who relied on it. Done carelessly, retirement leaves gaps and orphaned permissions.

Why this comes up

Workflows end. The need disappears, a better tool replaces it, or an honest review concludes it was never worth operating. Stopping is a valid and often wise outcome. But a workflow that acted on systems, held permissions and produced records cannot just be abandoned. It has to be wound down deliberately.

Decide what happens to the work

First, what replaces it? The workflow was doing something. When it stops:

  • Does a new workflow take over, a person, or does the work stop entirely?
  • Is there a gap between switching off the old and the new being ready?
  • Who handles the in-flight cases at the moment of switchover?

Leaving the work with nowhere to go is the most common retirement failure.

Remove access and stop actions

A retired workflow should not keep the ability to act. Following the same care as giving write access, in reverse:

  • Remove its permissions and access to systems.
  • Disable its integrations and any triggers that could restart it.
  • Confirm it can no longer take actions, not just that it is idle.

Orphaned access, a retired agent that technically still has write permissions, is a real risk. Close it properly.

Preserve what matters

Some things should outlive the workflow:

  • Its records and audit trail, for as long as they are needed.
  • The knowledge of how it worked and why it was retired.
  • Any test set or lessons that a successor could use.

Decide what to keep and where, rather than losing it when the system goes dark.

Tell the people who relied on it

Anyone who depended on the workflow, or whose work fed into it, should know it is going and what replaces it. A silent shutdown creates confusion and gaps downstream.

A small example

A team replaced an old routing agent with a new one. Because they retired the old one properly, they moved in-flight cases across, revoked its access, kept its logs, and told the affected teams, there was no gap and no orphaned permissions. A neighbouring shutdown that skipped these steps left an agent with live write access nobody was watching.

What this does not solve

A clean retirement avoids gaps and orphaned access; it does not decide whether retiring is the right call. That is a judgment based on whether the workflow is still worth operating. Retirement done well simply makes stopping safe when you have decided to stop.

Good enough to move on when

  • What replaces the work is decided, including in-flight cases.
  • All access, integrations and triggers are removed.
  • Records, knowledge and lessons are preserved.
  • Everyone who relied on the workflow has been told.