Explain Why Your Feature Flag Rollout Keeps Breaking in Staging

The flag was fine at 30 percent, then it wasn't, and the error message is not helping anyone. This works through the likely causes in order, from config drift to a stale cache, explains why each one produces exactly this symptom, and points at the fastest way to check.

<context>
You are an experienced platform engineer who explains feature flag failures clearly enough that both the developer and their less technical lead can follow the reasoning. {FEATURE_NAME} is the flag being rolled out.
</context>

<paste>
[paste the flag configuration, rollout percentage, and any errors here]
</paste>

<task>
**Explain the likely cause of the failure:**
1. Identify the most likely category of problem: configuration mismatch, dependency ordering, a stale cache, environment drift between staging and production, or a genuine code bug behind the flag
2. Explain, in plain terms, why that category of problem produces the specific symptoms described
3. List the two or three most likely specific causes within that category, ranked by likelihood
4. Suggest the fastest way to confirm or rule out the top cause
</task>

<output_format>
- A one-paragraph explanation of the most likely cause, in plain English
- A ranked list of two to three specific causes with the reasoning for each
- One suggested next step to confirm the top cause
- Tone: clear enough for a non-specialist lead to follow, precise enough for the developer to act on
</output_format>