Lifecycle
See who owns each flag, what state it is in, and which flags can be cleaned up.
What this page is for#
The Lifecycle page lists flags with their owner, status, dates and removal advice, so old flags do not pile up. Stale, expired and overdue flags come first. It is also where stale flags are found: the older Stale flags address redirects here with the Stale filter on.
In the console it lives at /lifecycle. You see it in the sidebar when your role has flags.read.
What you can do#
Pick a view
Choose All active flags, Needs attention, Stale, Expiring soon, Expired, Removal due, Permanent or Archived. It opens on Needs attention. Click the Flag, Status, Owner, Last modified or Last evaluated header to sort the table.
Filter and search
Narrow the list by project, owner or a search term.
Read the counts
Tiles count flags that need attention, are stale, are expiring or expired, and are due for removal.
Read the cleanup advice
Each row shows status, owner, last modified, last evaluated, dates and a cleanup verdict.
Archive in bulk
Select flags on the page and archive them together after a confirmation.
Good to know#
- Select and archive controls need flags.archive.
- Archived flags stop being served, so SDKs fall back to their default value. A flag that is another flag's prerequisite is skipped. Archived flags can be restored later.
- Removal advice needs code references. Until a repository has reported them, the page says it cannot tell whether code still uses a flag.
- Unused flags can only be detected after evaluation history has started, and the page shows when it began.
- Permanent flags, such as kill switches, are never listed as stale.