Administration
Read service readiness
Inspect readiness chips, understand their limits, and refresh the underlying checks.
Global administrators inspect service checks in Admin → Dashboard → Readiness, in the card also called Readiness.
Inspect a check
- Open the Readiness dashboard tab.
- Find the service's readiness chip.
- Select the chip to open its details.
- Read the state, explanation, Last updated, Missing configuration, and Check details.
- Review Recent operation signals for context.
- Select Close to return to the chip.
The details appear as a dialog on larger screens and a bottom flyout on mobile. Scroll its body when the explanation is long.
The chips cover database connectivity, File storage, Auth email, Notifications, Private-pay billing, Media worker, Text-to-speech provider, RAG AI, and application-route readiness.
Interpret the state
| State | Meaning |
|---|---|
| Ready | The checks performed for that service currently meet their readiness conditions. |
| Missing Config | A required service setting is missing or unsuitable; read the explanation. |
| Degraded | A service is disabled, incomplete, unavailable, or otherwise needs attention according to its check. |
| Loading or Unknown | A current readiness result is not yet available. |
The overall badge prioritizes Missing Config, then Degraded. Open individual chips to identify the cause.
A Ready badge is not a test of every user workflow. Some checks inspect configuration or recent worker signals; for example, File storage readiness does not itself upload a test file, and notification configuration does not prove that a particular message reached its recipient.
Private-pay billing includes invoice-service and email/SMS reminder readiness. An inactive reminder channel can produce Degraded while other functions remain available. Follow the specific check rather than treating every degraded state as a complete outage.
Refresh and investigate
Return to Overview, select Refresh, then reopen Readiness. Check the new Last updated value. Opening a chip or switching dashboard tabs does not itself rerun the checks.
Recent operation signals are shared across the readiness results; they are not restricted to the chip you opened. The flyout shows up to eight of them. They are contextual summaries, not a complete activity history. Use Audit for recorded events.
These details provide inspection, not controls for changing service configuration. Ask the administrator responsible for the affected service to resolve configuration or repeated availability problems. Then refresh and retry the affected workflow when appropriate.
Readiness is separate from backup preflight, RAG metrics, and Help synchronization.