# Flag enabled for wrong segment: pre-release checklist

Source: https://releasefailures.com/incidents/flag-enabled-for-wrong-segment/
Content version: 1.0.0
Verified on: 2026-10-21
Licence: CC BY 4.0

Definition: A feature flag targets the wrong users, region or percentage after a rule edit.
- [ ] PR-01 List the audience every changed flag rule resolves to and confirm internal-test flags resolve only to internal accounts, not to every first-party application. (test class: Configuration and environment tests)
- [ ] PR-02 Evaluate each version-based flag rule against the targeted environment's version and confirm the solution's current app-builder version does not change the result. (test class: Configuration and environment tests)
- [ ] PR-03 Simulate the weekly automatic upgrade of a development environment and confirm no flag changes state without a customer deploy. (test class: Configuration and environment tests)
- [ ] PR-04 Run the new-user login flow on the Android and iOS apps with each changed flag set to its production audience. (test class: End-to-end tests)
- [ ] PR-05 Create and edit a team with an external identity provider group selected, then reload the team page and confirm the group link was saved. (test class: End-to-end tests)
- [ ] PR-06 Run the flagged feature's end-to-end tests with the flag on and off for an account in each targeted release channel. (test class: End-to-end tests)
- [ ] PR-07 Roll a targeting change out to one release channel at a time and hold each step until that channel's support ticket volume stays at its baseline. (test class: Canary and progressive delivery checks)
- [ ] PR-08 Compare a behaviour metric of the flagged feature, such as saved group links, between flagged and unflagged accounts before widening the rollout. (test class: Canary and progressive delivery checks)