TYPO3 v12 Cache Tag Invalidation Breaks with Non‑Taggable PSR‑6 Backends

Direct answer

Assign a taggable backend—typically RedisBackend or TYPO3's database backend—to every cache that core invalidates by tag, including cache_pages, content-element caches, and Extbase persistence caches. Do not point those caches at generic PSR-6 adapters such as object-storage or cloud-SDK pools, because they cannot implement TYPO3's tag contract.

Likely explanation versus confirmed facts

Likely explanation: flushByTag() requires the cache backend to expose TYPO3's taggable cache contract. A generic PSR-6 pool has no mapping from tags to storage keys, so the cache factory either raises UnsupportedOperationException or silently skips invalidation, leaving stale page or Extbase entries after content changes.

Confirmed facts for TYPO3 v12: the Caching Framework uses PSR-6/PSR-16, and tag-based flushing depends on the backend implementing the taggable contract. RedisBackend implements tags through Redis sets. TYPO3 core does not provide an automatic fallback, production health check, or deprecation warning for non-taggable backends.

Steps for this case

1. Identify the affected caches in AdditionalConfiguration.php or system settings: cache_pages, content-element cache configurations, and Extbase persistence caches.
2. Replace any non-taggable backend with RedisBackend or another backend known to implement the taggable contract, and supply host, port, database, password, timeout, and compression options supported by your Redis instance.
3. Clear TYPO3 caches after changing backend assignments.
4. Run a controlled probe: write an entry under a unique tag, call flushByTag() for that tag, then read the same identifier and confirm the entry is missing or regenerated.
5. Review system and deprecation logs for UnsupportedOperationException or tag-related warnings after publishing content.

Safe verification command

# Example only; adapt paths and credentials to your environment.
# This inspects configuration, it does not modify production data.
grep -R "cache_backend" AdditionalConfiguration.php config/system/settings.php 2>/dev/null || true

Assumptions and uncertainty

• Managed Redis services such as AWS ElastiCache or Azure Cache for Redis can work only if they expose the Redis commands RedisBackend uses and allow the configured connection options; command restrictions or TLS requirements may break tag handling.
• No core-level fallback or health-check mechanism is confirmed for current or future TYPO3 releases; do not depend on one until release notes state otherwise.
• This guidance assumes you can edit TYPO3 configuration. If you cannot, the recommendation changes to requesting backend reassignment from your platform administrator.

Missing diagnostic detail: Can you modify AdditionalConfiguration.php or equivalent system configuration to reassign cache backends? This determines whether the fix is a configuration change or a support request.