Inngest health

Two server-side probes fire on each page load: GET /health on the inngest-server (liveness), and POST /e/<event-key> with a no-op system.health.beacon event (key validity). The second probe matches the exact ingest path the "event key not recognized" rejection spam takes — rejected here means our key is wrong; accepted here means the spam is from some other sender with a different (wrong) key.

Checked: 6/22/2026, 12:08:51 PM · auto-refreshes every 60s