Health Check List

Preview in your theme

A doctor that really runs. Press “Run all checks”: eight probes start at once and land out of order between 0.42s and 1.8s, each writing only its own row while the summary recounts live. The result is 5 passed · 1 warning · 2 failed, so the verdict reads “2 blocking issues”. One polite live region speaks twice for the whole run — “Running 8 checks…” then “Finished: …” — never once per row. Fix actions only appear once a row has actually reported a problem: “Install acme-cli” is a real one that removes itself, prints a confirmation under the list, and makes that probe resolve to Passed on Retry; the other is a link to /docs.

Not checked yet

8 pending

Node.js 20 or newerNot checked
Required by the build toolchain
Package managerNot checked
pnpm 9+, corepack enabled
Environment variablesNot checked
Secrets the server reads at boot
Free disk spaceNot checked
A cold build writes roughly 8 GB
acme-cli on PATHNot checked
Used for deploys and log tailing
Database reachableNot checked
postgres://localhost:5432/acme_dev
Git working treeNot checked
Deploys refuse to run from a dirty tree
Port 3000 availableNot checked
The dev server binds it on start

Per-row re-runs. “Webhook endpoint reachable” opens Failed with the recorded ETIMEDOUT — press Retry on that row alone and only it flips to Checking, then Passed after 0.6s, while the other two rows keep their verdicts. The DNS row demonstrates the stale-answer guard: press Retry (attempt 1 takes 1.5s and ends in SERVFAIL), then press Restart while it is still spinning. Attempt 2 settles as Passed after 0.35s, and when attempt 1's failure finally arrives it is discarded instead of flipping the row back to Failed.

1 blocking issue

1 passed · 1 failed · 1 pending

TLS certificatePassed
hooks.acme.dev · expires in 61 days

Webhook endpoint reachableFailed

The receiver was down during the last run

POST https://hooks.acme.dev/v2/ingest
connect ETIMEDOUT 203.0.113.41:443 after 10000ms

Last successful delivery: 4 hours ago

DNS resolves (slow first attempt)Not checked
First attempt takes 1.5s and fails; every later attempt takes 0.35s and passes

DNS probe attempts started: 0

The all-clear, as a read-only report — statuses come straight from the server, no check carries a run() and neither onRunAll nor onRetry is passed, so no Run all / Retry control is rendered at all rather than a button that does nothing. The verdict reads “All checks passed”, and the workers row still keeps its evidence behind “Show detail”.

All checks passed

5 passed

API respondsPassed
GET /v1/health

Background workersPassed

4 of 4 workers heartbeating

worker-01  last beat 2s ago
worker-02  last beat 1s ago
worker-03  last beat 3s ago
worker-04  last beat 1s ago

Queue depth under 1kPassed
112 jobs waiting
Migrations appliedPassed
head = 20260714_add_seats
Redis reachablePassed
redis://cache.internal:6379

Skipped mixed in, with defaultExpandedIds={['retention']} so the warning panel starts open. Skipped rows carry a dash plus the word “Skipped” — they are a decision, not a failure, and they are counted apart from the rest (3 passed · 1 warning · 2 skipped, verdict “Ready, with 1 warning”). The warning row offers a docs link as its fix; nothing here is re-runnable, so no Retry buttons appear. The registry row carries a 77-character label and a 57-character unbreakable token in its description: both wrap inside the card instead of widening it.

Ready, with 1 warning

3 passed · 1 warning · 2 skipped

Auth provider configuredPassed
WorkOS · 2 connections
Nightly S3 backupsSkipped
Not available on the Team plan — upgrade to enable
Container registry credentials for ghcr.io/acme-platform/edge-runtime-builderPassed
Reading the deploy key AKIAIOSFODNN7EXAMPLEQ4W9RTYUIOPASDFGHJKLZXCVBNM1234567890 from the org secret store

Legacy v1 API compatibilitySkipped

Skipped: the v1 shim was removed in release 2025.3, so there is nothing left to probe.

Log retention windowWarning
Compliance asks for 90 days
Retention settings docs
```
Retention is set to 30 days on 2 of 5 regions (eu-central-1, ap-southeast-2).
```
Custom domain SSLPassed
app.acme.com · auto-renewing

status “loading”: the list of checks itself has not arrived yet, which is not the same as checks that have not run. Three skeleton rows stand in for it, the root carries aria-busy, and no Run all control is offered until there is something to run.

status “error”: the list could not be fetched at all. Nothing was probed, so there is no verdict and no counts line: just the reason (errorMessage) in a role “alert” panel and a Try again button wired to onReload, whose calls are counted below.

Could not load the checks

GET /v1/health/checks returned 503 Service Unavailable after 3 attempts.

onReload calls: 0

status “empty”: the server answered with no checks configured for this project. A plain line instead of an empty summary header over an empty list.

No checks configured.

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro