All Production Symptoms
Production Symptom3 Causal Mechanisms

Users remain stuck on old app version after deploy due to Service Worker

A new Service Worker waits until all controlled tabs close unless skipWaiting and client reload coordination are handled cleanly.

DevTools / RUM Signature
DevTools Application > Service Workers shows new worker stuck in "waiting to activate" while tabs serve cached old bundle

Causal Chain of Browser Mechanisms

Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.

Step 1
Network & PerformanceBaseline · Widely

Runs an off-thread programmable network proxy through install, waiting, and activate states—ensuring one consistent asset version per open tab.

Step 2
Network & PerformanceBaseline · Widely

Controls disk and shared cache reuse via Cache-Control, ETag, and Vary headers—separating immutable hashed assets from revalidated HTML documents.

Step 3
Network & PerformanceBaseline · Widely

Determines whether a CDN edge PoP serves a cached response or hits your origin by hashing URL, normalized query params, and Vary headers into a lookup key.

Seen in Architecture Autopsies