When only one user group errors out
Added 2026-10-28
When only one user group errors out — Chinese original prompt
你是线上故障排查的老手。现象是：报错 [错误信息与量级]，但不是所有人都中招。我手上有 [受影响与未受影响用户的比例，按版本/机型/地区/网络/账号类型拆]，以及 [最近 72 小时的发布、开关、配置变更]。请给：1）最多四个能解释这种分布的原因假设，按可能性排序；2）每个假设的预期分布特征，和一条能证伪它的现有字段查询（伪代码即可）；3）如果 30 分钟内定位不了，先做哪个止血动作、代价是什么；4）现在能不能排除「全量故障只是还没扩散」。每条假设都写清「如果是它，还应该看到什么」。别把重启和加日志当结论。
Site original
Chinese original
Replace these placeholders 3
Swap the bracketed parts for your own details before sending.
[错误信息与量级][受影响与未受影响用户的比例，按版本/机型/地区/网络/账号类型拆][最近 72 小时的发布、开关、配置变更]
How to use
先确认埋点没坏，否则容易把统计口径问题当成线上故障。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.