Stale flag management helps you maintain a clean codebase by identifying feature flags that have either been completely rolled out or have been rolled back for a specific period of time.
A feature flag or experiment becomes stale when it meets one of these conditions:
After a flag or experiment becomes stale, it's ready for cleanup. This means you can remove the flag from your codebase and archive it in Amplitude.
When you're looking at the list of your flags or experiments, a status badge appears next to the flag indicating that it's stale. Hover over the stale badge to view when it became stale and update the stale date if needed.
In the Feature Flags or Experiments list, the stale status appears as a secondary status badge next to the primary status. Click the Stale option which filters the table to show only stale flags.
Hover over the Stale badge on a flag. Information appears that displays when that specific flag became stale. The information pop-up contains information on the rollout status of the flag. From this pop-up, you can choose to archive the flag or to unmark the flag as stale.
By default, Amplitude marks a flag or experiment stale after 30 days from the date of the last update. For example, you set the rollout of a flag to 100% on March 1. If no other updates occur, Amplitude marks the flag as stale 30 days later, or in this example, March 31. If you deselect the stale value, Amplitude considers the flag permanent and won't mark the flag stale again.
If you change the rollout after you set a stale date, you can update the stale date. For example:
You can receive notifications when flags or experiments become stale. If you are an owner of a flag or experiment, Amplitude sends a message about any flag or experiment that becomes stale over the previous 24 hours. These notifications are sent once each day.
You can receive notifications through:
Configure notification preferences in your organization settings.
After a flag or experiment becomes stale, remove it from your list.
If a flag or experiment has multiple variants and one variant is rolled out to 100%, keep that variant in your application while removing the others. This ensures the winning variant remains active.
You can use Amplitude AI or Amplitude MCP to highlight stale flags and either update the stale date or archive them. Within the agent window, ask Amplitude to generate a list of your stale flags. After it gives you the list, you can continue the conversation to archive or modify your stale flags.
March 18th, 2026
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2026 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.