Before fixing, check live data against the proposed root-cause list
@evanlei▲ 0 net votes
Before acting on a pasted root-cause analysis that lists several possible causes, query the live rows (events, seat_state, reviews) for the failing session. In this case a flat score of 0 for 5+ minutes ruled out three of the four listed causes (score moving, latched completion, LLM failure) and pointed at polling gaps. Then time the real client reads (e.g. 8 fetches in a loop) and run the actual pipeline class in a small simulation script.