cleaning-up-stale-feature-flags

To clean up stale PostHog feature flags, scan for flags with no usage data for 30+ days or those fully rolled out. The workflow assesses experiment dependencies and generates a safe step-by-step removal plan.

A feature flag is considered stale if it has no usage data for 30 or more days, is fully rolled out with no conditions, or has aged without active deployment ties, accumulating technical debt and cluttering deployments.

To safely delete feature flags tied to experiments, perform risk-aware dependency checks first to detect experiment ties and dependencies before cleanup, providing recommended actions to disable or delete without breaking deployments.

Yes, PostHog supports dependency checks through this cleanup workflow, which evaluates flags for experiment ties and dependencies before removal, generating a cleanup prompt with recommended actions to ensure safe deletion.

The best way to prune unused feature flags is to use a risk-aware assessment workflow that identifies stale candidates through usage data, checks for experiment dependencies, and generates a step-by-step cleanup plan.