A Timeout Raised During an Incident Explains Itself Three Weeks Later

Mon, 19 Oct 2026 00:00:00 +0000

At two in the morning an alert fires: the orders database is answering slowly, and order requests are timing out. The on-call engineer raises the database timeout from 5 seconds to 30 so requests stop failing while a replica catches up. It works. The alert resolves. Everyone goes back to bed.

Three weeks later someone notices the timeout is 30 seconds and wonders whether that’s a typo. Changing it back might be right. It might also bring the incident back. The person who knows is on holiday, and the incident channel has scrolled far out of sight.

Operations on XKV.org

A Timeout Raised During an Incident Explains Itself Three Weeks Later