Operations
Cache management
Refresh application caches from the dashboard without deleting content or private security state.
On this page
Dashboard workflow
Administrators can request a cache refresh through the Cache screen or toolbar shortcut. The dashboard shows whether a refresh is pending and the last completed refresh. Requests require CSRF protection and are limited to once every 30 seconds. The refresh is queued through a private marker and runs before the next Symfony container boot. It does not delete compiled container directories still used by in-flight requests.
What is refreshed
The operation clears bounded Twig, translation and cache-pool data and rebuilds the relevant container and route entry files in the configured environment. It preserves sessions, rate-limit state, uploaded media, site settings and the database. A dashboard refresh is not a destructive reset or a data-recovery procedure. Do not delete the whole private runtime directory to imitate a cache clear.
What it cannot clear
- The visitor's browser cache or cached DNS answers.
- A reverse proxy or CDN operated by the hosting provider.
- Provider-side caches or a separate frontend deployment.
- An incorrect domain record, TLS certificate or document root.
If stale content persists, identify the cache layer and check whether the change was actually saved. After a code deployment, follow the release's cache procedure rather than repeatedly clicking refresh.
Something unclear? Contact me about this guide.