Message-loss fix failed silently due to a timestamp format bug
A team noticed messages were occasionally being lost and built timestamp-based polling to recover them. The poller sent local-timezone timestamps, which the provider's API rejected with validation errors on every request, so the fix never ran in production. An unrelated automated audit detected that the poller had never succeeded. In a separate incident, a delivery-tracking update was deployed to one copy of a send script but not to a duplicate running on another server, which an automated patrol also caught. The team resolved both by converting timestamps to UTC at the API boundary and unifying the duplicate scripts into a single source.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in