Surface Redis eviction policy misconfiguration in UI / system health (noeviction required)

[erhathaway]

Describe the feature or potential improvement

Given that maxmemory-policy=noeviction is a hard requirement, it would be very helpful to surface this more prominently, for example:

A persistent warning banner in the UI

A red health check / system status indicator

Or a blocking startup warning in self-hosted mode when Redis is misconfigured

Suggested message:

Redis eviction policy is not noeviction. Queue jobs may be lost and ingestion may fail. Please update your Redis configuration.

Why this matters

This class of misconfiguration causes subtle, time-consuming failures that are difficult to diagnose, especially for new self-hosted users. Making it visible at the UI / health level would prevent silent data loss and significantly reduce operational friction.

Additional information

No response

[Steffen911]

@erhathaway As far as I'm aware, bullmq is very noisy in system logs about this behaviour and the expected issues. Additionally, in most cases other caching policies should work as well.
Did you observe any specific problems due to the caching policy? if yes, which problems and which policy did you have in place?