One service configured its cache with a name where a number belongs

A service set its cache database index to the deployment name instead of a number. The field takes a numeric index, so the value was never valid.

The result was that the service wrote nothing to its cache at all, despite caching being switched on in its configuration - the instance held no keys in any database. Like the hostname fault filed alongside this, it failed silently and looked like a healthy but unused cache.

Fixed on 2026-08-19 while enabling authentication across the caching layer. The service now connects and authenticates correctly.