SIGNALS Docs
Reader View

Caching

Cache backend health, hit/miss stats, TTL preferences, and manual domain invalidation.

Overview

The Caching panel monitors the application cache and lets permitted admins flush tagged domains.

Where it lives

Route: /admin/settings/caching (admin.settings.caching)

Open Admin → System → Caching. Requires settings.manage.

Sections

  1. Warehouse health — driver, tag support, Redis/database probe
  2. Hit/miss stats — per-domain counters
  3. TTL preferences — navigation, widgets, insights, exchange rates
  4. Manual invalidation — confirm + audit-logged flush per domain

Indefinite domains (settings, registries, translations) are read-only with documented invalidation triggers. Cache backend switching is not offered on Cloud, where the warehouse-health summary also identifies queues as managed by Signals Cloud.

At a glance

Monitor and operate the application cache. Requires settings.manage. See the developer Caching Strategy page.

Section Purpose
Warehouse health Active driver, tag support, Redis latency/keys/memory (when Redis), or cache-table size (database driver)
Hit / miss stats Cheap counters for settings, navigation, widgets, custom fields, registries, insights, and i18n
TTL preferences Bounded TTLs for navigation, widgets, insights, and exchange rates
Manual invalidation Permission-gated, audit-logged flush buttons per domain

Indefinite domains (settings, registries, translations) are shown read-only with their invalidation triggers — they have no tunable TTL. On Signals Cloud the panel remains available; cache repository switching is never offered (hosting is env-driven).