Slab incident

Increased occurrence of "Still trying to save..." message while editing posts

Minor Resolved View vendor source →

Slab experienced a minor incident on January 8, 2024, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 08, 2024, 11:08 PM UTC
Resolved
Jan 08, 2024, 11:08 PM UTC
Duration
Detected by Pingoru
Jan 08, 2024, 11:08 PM UTC

Update timeline

  1. resolved Jan 08, 2024, 11:08 PM UTC

    Type: Incident Duration: 10 days, 20 hours and 34 minutes Affected Components: Application Jan 8, 23:08:00 GMT+0 - Investigating - The post should eventually save and there is no system degradation or increased failure to save. We are investigating why our application client is not attempting to save immediately or sooner when it could and should. Jan 12, 21:39:00 GMT+0 - Identified - A potential root cause has been identified. Jan 14, 16:16:00 GMT+0 - Identified - A potential fix has been implemented. Jan 15, 02:37:00 GMT+0 - Identified - The potential fix has been tested on our staging environment, and the fix is now awaiting deployment. Jan 16, 02:28:00 GMT+0 - Monitoring - The fix has been deployed and we are currently monitoring the result. Jan 17, 18:32:57 GMT+0 - Monitoring - We have observed the expected subsequent drop in the slow save warning events and will continue monitoring this and related metrics. Jan 19, 19:42:00 GMT+0 - Resolved - Relevant metrics have remained normal for three full days and we consider the incident resolved. The root cause was a recent minor version library upgrade that included performance enhancements, but also an unexpected side effect on how we handled reconnections, particularly when a computer wakes up from sleep. Our team was able to adjust for the upgrade change, so reconnections would again be immediate, resulting in faster post saving like before.