Automated Split Stale Feature Flag Cleanup
Every Monday, WebRun opens Split, checks every feature flag's rollout percentage and last-changed date, logs the stale ones to a Google Sheet, and posts a Notion checklist so engineering can archive them before the flag list gets unmanageable.
How do I find and clean up stale feature flags in Split?
WebRun reviews every feature flag in Split each Monday, finds the ones sitting at a fixed rollout with no changes in 30 days, and logs them to a Google Sheet with their state and last-changed date. It then posts a Notion cleanup checklist so engineering can archive stale flags before the flag list gets unmanageable.
- Stale flags get caught every week instead of piling up for months
- Engineering opens Notion to a ready-made cleanup checklist
- The flag list stays lean because rollout state is checked automatically every week
Built for Engineering teams · platform engineers · DevOps leads · product engineering managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.split.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Split - find stale flags
- Open Split and list every feature flag across environments
- Check each flag's rollout percentage and the date it last changed
- Flag anything sitting at a fixed 100 percent or 0 percent rollout with no change in 30 days
Done when Every stale flag is identified with its rollout state and last-changed date.
-
2
Notion - log the cleanup list
notion.so
WebRun opens Notion to post the cleanup checklist. - Open the engineering cleanup page in Notion
- Post this week's stale-flag checklist with one line per flag and a link to its Split detail page
- Note which flags look safe to archive versus still needing a decision
Done when Engineering has a Notion checklist of stale flags to review and archive.
-
3
Google Sheets - post the cleanup checklist
google.com
WebRun opens Google Sheets to log the cleanup list. - Open the Split flag cleanup sheet
- Add a row for each stale flag with its name, environment, rollout state, and last-changed date
- Mark rows already logged in a prior week as still open instead of duplicating them
Done when The sheet lists every stale flag currently open for cleanup.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun delete or archive the flags itself?
No. WebRun only builds the cleanup list. Archiving or deleting a flag in Split is left for an engineer to confirm and do by hand.
How does it decide a flag is stale?
It checks the rollout percentage and the last-changed date in Split, flagging anything fixed at 100 percent or 0 percent with no change in the last 30 days.
What if a flag is deliberately kept at 100 percent?
It still gets listed for visibility, but the Notion checklist makes clear these are candidates to review, not flags that were changed automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.