The Journey Graveyard: Campaigns Nobody Dares to Turn Off

Publication date: October 30, 2026

The inventory contains three old friends: Campaign_Final_v7, Journey_New_Good, and Test_Do_Not_Delete. Their creator moved teams long ago, nobody can find the original brief, and all three journeys are still there. Asking whether we can turn them off produces the kind of silence usually reserved for suspense movies.

Most marketing operations eventually acquire mysterious journeys named Campaign_Final_v7, New_Journey_Actually_Final, and Test_Do_Not_Delete. Nobody remembers who built them, and nobody dares turn them off. Launching is celebrated. Retirement rarely gets a meeting invite.

Nobody wants to press Stop

Old journeys may rely on outdated rules, retired data sources, incorrect audiences, or failing custom actions. The cost goes beyond maintenance: customers can receive contradictory outreach from automations the team barely remembers.

That silence has a price. A forgotten journey does not just take up space: it may send obsolete messages, depend on retired sources, or contradict a newer campaign. The trouble rarely fits on one screen.

Adobe's 2026 release notes describe hygiene analysis capabilities for identifying broken configurations, silent failures, and aging assets. Tools can surface problems, but teams still need owners, lifecycle rules, change controls, and retirement criteria. AI can find the mess. People must decide what stays.

A guided tour of the journey museum

Review active and draft journeys, usage, owners, external dependencies, repeat errors, outcomes, and the next review date. Classify each as keep, optimize, pause, or retire. Record why, and understand downstream effects before changing anything.

Maybe next month’s most useful ritual will not be launching another automation. It may be opening the inventory and asking one simple question about each journey: if it did not exist today, would anyone ask to build it again?

Adobe Journey Optimizer release notes: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/whats-new/release-notes