Multiple caches stack
A typical production site combines page HTML cache (plugin or reverse proxy), object cache for queries and fragments (Redis via drop-in or plugin), opcode cache (PHP OPcache), browser cache, and a CDN. Clearing only one layer leaves stale HTML or assets elsewhere—identify which layer served the outdated response using response headers and timestamps.
Practical order
| Layer | How | Watch for |
|---|---|---|
| Object cache | wp cache flush (WP-CLI) or plugin button | WooCommerce sessions, cart fragments |
| Page cache | Plugin purge / Nginx helper | Mobile vs desktop variants |
| OPcache | php-fpm reload or opcache_reset in controlled context | Brief latency blip |
| CDN | Plugin webhook or dashboard purge | API rate limits |
Transients and cron
Some “stuck” admin notices are transients in the database—use dedicated cleanup tools or WP-CLI transient delete --all cautiously. Do not confuse them with Redis object cache entries.
Related: Clear Redis cache, Clear Cloudflare cache, Clear nginx cache, Clear browser cache.