日报的数字和数据库对不上
日报比后台少 0.3%，每天都少，同步任务从没报过错。
Copy the prompt, then pick a model. It plays the interviewer and asks you through it scene by scene instead of handing you the answer.
On a phone with the app installed, the system opens the app directly. Links cannot open external apps inside WeChat — open it in a browser first.
数据对不上的时候，前三个动作是固定的，而且都不需要读代码：差多少条、差的方向是不是稳定、抽十条差异记录出来看。第三步经常直接给出答案。
大多数人会先去读同步任务的代码——可能要读几百行、看半小时；而抽十条记录一眼看出共同点，只要一分钟。
这一份不需要任何系统知识，产品和数据的同学也能做。现场里摆了三个「数据对不上」的经典嫌疑人，全都是干净的。
The move this one drills
Have you done this one?
Sign in to mark this one as practised — next time you come back you'll see when you did it.
Notes from people who did this one
How to use this
It gives you the scene (what the service is, the symptom, when it started, the blast radius) and then goes quiet. You ask questions, request metrics, logs, packet captures, propose hypotheses — it answers from a truth you cannot see.
**It is not allowed to volunteer where to look next.** If you don't ask, it doesn't say — even if you circle for ten minutes. That's deliberate: in real life nobody stands next to you saying "maybe check the flame graph". Troubleshooting *is* the skill of knowing what to ask.
How to start
- Pick one, open it, copy the prompt.
- Paste it into a brand-new conversation.
- It gives you the scene and stops — **now it's your turn to speak.**
Four commands you can call out at any time
给个方向give me a direction, not the answer (counted in the tally)公布真相reveal the truth and wrap up换一个start over with a different incident复盘wrap up now and print the review card
Three traps
- Don't read the truth at the end first — that ruins the whole thing.
- Don't start by guessing the cause. Establish the scope first (how much, which part, when it started); scope tells you whether this is a code problem or an environment problem.
- Every scene has planted false leads: an unrelated deploy at the same time, metrics that are effects rather than causes, the textbook suspect waiting for you. The wrap-up tells you how many questions you spent on each.
Start with the P99 one — its diagnostic chain is the cleanest. Then "only some machines", whose lesson is the most reusable of all. Save the intermittent timeout for later: its answer lives outside your own system. The report mismatch needs no systems knowledge at all.
Sign in to write a note.