Stale flag detection

You know some of your feature flags are no longer needed, but it can be tricky to work out which ones.

To help, we’ve added automatic stale flag detection. A series of checks that monitor your flags, highlighting when they’re no longer needed. We run three checks looking to see if:

• The feature has been rolled out to everyone. You can specify the number of days after which you’re confident the feature is working fine and this check will pass.

• Flag code has been removed. Either automatically, using AI flag cleanup, or manually. This check passes once there’s no flag references left in your repo.

• Access checks haven't run recently. You can set how long to wait without someone accessing the feature before the check passes.

Once the checks pass, the flag is marked as stale (shown with a little broom next to their name) and it’s added to the stale flag view - a list where you can see all the features that are currently stale, as well as what needs to be done before they can be archived.

Of course, not all flags need to be cleaned up. You can mark a flag as permanent if you want to keep it indefinitely, useful for Ops flags or for user entitlements.

Stale flag detection is the second announcement this week to bring you closer to zero maintenance feature flagging. Check out our launch week page for what’s new each day this week.

Start using stale flag detection by configuring your defaults in the settings, or check out the docs for more information.