agent active Last verified 2026-03-29

Stale Deploy and Cache Issues

Runbook for old bundles, wrong host delivery, stale service workers, and mismatched Pages/worker routes.

Owners
platform-experience
Source Repos
Applications/TopoloOne, Websites/docs
Systems
TopoloOne, Topolo Platform
Tags
runbook, deploy, cache, service-worker

What It Is

Use this runbook when a hostname keeps serving an older UI, route, or static asset after a deploy.

How It Works

Stale deploy issues normally come from one of four places: old service workers, wrong Pages custom-domain binding, wrong worker route, or an asset shell that is still serving a previous bundle.

Interfaces

  • Cloudflare Pages deploy output
  • worker route config
  • service-worker registration logic
  • browser network inspector

Data Flow

  1. Browser requests the hostname.
  2. The hostname resolves to Pages, a worker route, or both.
  3. Cached HTML or service workers may pin the browser to an older asset graph.

Failure Modes

  • service worker still controls the tab
  • hostname is bound to the wrong Pages project or worker route
  • stale index.html serves an old asset hash
  • deploy succeeded but the custom domain still points elsewhere

Debugging

  • confirm which runtime is actually serving the hostname
  • inspect the live HTML for the asset hash being served
  • verify worker routes and Pages domain bindings
  • check whether a service worker is still controlling the page

Change Log / Verification

  • Verified against the TopoloOne delivery fixes on 2026-03-29