Workers and Redis in the WebUI

The operational WebUI can show worker state and Redis-backed system information using its configured service connections. Connection values, node addresses and credentials remain private to the installation.

Worker state

Workers enroll and report heartbeats. A heartbeat indicates recently reported state; it does not prove every routine is healthy. Inspect routine status, schedule state, job results and logs together. Lifecycle buttons dispatch commands through WorkerPool rather than launching an untracked process directly.

Redis inspection

Use a restricted account and the permissions required by your deployment. Keep cluster members and connection strings in the approved configuration store. Public screenshots should use a disposable service with illustrative keys and values.

Browser behavior

Test filtering, refresh, empty states and unavailable backends. Permission errors must remain visible and must not cause automatic mutation retries. Read-only browsing and commands that change worker or cache state require separate acceptance checks.

See Redis caches, batch jobs and API operations for the underlying behavior.