Dynamic configs can live for years without a clear cleanup point. Teams can now find likely cleanup candidates, understand why they were flagged, and decide what to do next.
Temporary, Permanent, and Stale lifecycle states, with filtering in the Dynamic Config catalog
Reason-specific guidance on the config page: configs with no recent checks can be archived, while intentionally long-lived configs can be marked Permanent
A team-defined inactivity window (15, 30, 60, or 90 days; 30 by default)
Periodic email, in-app, and Slack reminders based on notification preferences
Lifecycle fields and filters in the Console API
Note: This is advisory only. A stale label does not change evaluation, disable a config, or archive anything automatically. This rollout does not include Feature Gate-only automation such as auto-archive, code-cleanup prompts or PRs, or bulk cleanup.
This closes a governance gap that several customers have raised and makes cleanup easier without introducing runtime risk.
Check out the Feature Management page in your Statsig Console to evaluate config staleness.