Databases & caching · Production incident
Saved, and the old value is still there
A user saves a change and the next page still shows the old value. How do you make sure users see their own writes?
Monday 11:15 · profile-serviceIllustrative scenario, not a real incident
Support: 140 tickets this month saying that a profile change did not save
A user edits their display name and presses save. The service answers with a redirect to the profile page, and that page shows the old name. A reload a little later shows the new one.
The profile service stores its data in PostgreSQL. Three weeks ago the platform team changed how its queries reach the database, to take load off it. The tickets began in the same week.
What the dashboards and logs show
- Save requests
- all return 303, with no errors in the log
- Stored value
- correct whenever support looks, minutes later
- After a reload
- the new value appears, sometimes on the second try
- Tickets by time
- most arrive in the ten minutes after each hour
Clarify · optional · scored under "Hypothesis before change"
Ask the interviewer
0 of 3 asked
Each question reveals a fact. What you ask before you act is part of your score.
First move · scored under "Mitigate before root cause"
Tickets keep arriving after every hour. What do you do first?
Your rubric score, the model answer, the follow-up questions and the related lessons appear once you have answered the last step.