One config edit takes the whole fleet down in thirty seconds
A rate-limit value lives in a central configuration service polled by every instance every 30 seconds. An engineer edited it through the web UI and added a trailing space. The value parsed to zero, every request was rejected fleet-wide within half a minute, and the UI shows no record of the previous value. Fix the system, not the typo.
The fix that looks right
Fixing it by trimming whitespace on read. It removes this exact failure and leaves the mechanism intact: unreviewed, unvalidated, unversioned, instantly global. The next incident is the same shape with a plausible number instead of a space — someone types 10 instead of 1000 — and no amount of string trimming catches it. Sanitising the input treats the typo as the cause, when the cause is a change path with no controls on it.