Twelve Minutes After Deploy, Old Code Woke Up
At 10:00 UTC, CI deployed a routine workspace schema migration ( v2 ) with new content-hashed JavaScript bundles and pruned old v1 chunks from the CDN bucket. Fresh incognito smoke tests passed in seconds.
Twelve minutes later, RUM telemetry and support tickets lit up. Users with long-lived sessions were hitting ChunkLoadError when opening a second tab, and worse, offline drafts were vanishing after users hit the browser Back button from an OAuth redirect.
T+00:00 : [email protected] rolls out; CDN purges v1 lazy chunks.
T+04:00 : ChunkLoadError rate spikes to 4.8% among users who opened a second tab after the deploy.
T+12:00 : 310 support tickets report missing offline drafts after users clicked Back from an external OAuth redirect.
T+18:00 : IndexedDB telemetry confirms v1 tabs writing deprecated record shapes into v2 object stores.
Why skipWaiting() and reload() Made It Worse
The first Slack reflex was to call self.skipWaiting() inside theβ¦