Volleyball Elite Academy development update

Volleyball Elite Academy Diagnose Resend webhook outage Diagnose Resend webhook outage Volleyball Elite Academy — Development Update • May 13, 2026 Diagnose Resend webhook outage What & Why On May 11 the daily webhook health alert fired with subject "[Action needed] Resend webhook stopped firing", meaning emails are still being sent through Resend but no / / events have come back into in the alert window. While this stays broken, every row in the SuperAdmin email log shows a stale "sent" status and bounces silently disappear. This task is a triage / diagnosis pass — find the root cause and either fix it directly if it's a config drift, or write up exactly what needs to change in the Resend dashboard. Done looks like A short written diagnosis (in the task completion message) covering: - Timestamp of the most recent successful webhook event in and how long ago that was. - Whether is currently set in production. - Whether the webhook endpoint is still registered and enabled in the Resend dashboard, and whether Resend's delivery log shows recent attempts being rejected (and with what status code). - The identified root cause (one of: secret rotated/missing, endpoint URL stale, Resend auto-disabled the webhook after failures, signature mismatch from a code change, or "still investigating"). If the cause is a config drift the agent can fix without code changes (e.g. secret restored from the Resend dashboard, endpoint re-enabled, URL updated), it is fixed and the next test event flows through. If it requires the user to take an action in the Resend dashboard, the task completion message gives them the exact steps. The daily webhook health alert stops firing for the warning kind on the next scheduler tick after the fix lands (or the user is told the alert will clear on its own once events resume). Out of scope Any UI work on the email log to indicate stale status (covered by the separate "stale event status badge" task). Changing the alert threshold, dedupe window, or snooze behaviour — only fix the underlying outage. Backfilling missed delivery/open/bounce events for emails sent during the outage window (not currently supported by Resend's API). Steps 1. Pull the diagnostic snapshot — Query for the most recent event timestamp grouped by event type, and for the count of emails sent in the alert window vs events received. Confirm the numbers that triggered the alert. 2. Check the secret and endpoint config — Verify is present in the production environment via the secrets workflow (do not print the value). Confirm the registered webhook URL in the Resend dashboard matches the production route. 3. Inspect Resend's delivery log — Look at the webhook delivery attempts in the Resend dashboard for the last 7 days. Note the HTTP status codes Resend is seeing. A run of 4xx or 5xx responses usually means Resend has auto-disabled the endpoint. 4. Apply or document the fix — If the cause is something the agent can resolve in code or config (re-register the endpoint, restore a missing secret via the secrets workflow, fix a signature-verification regression), do it. Otherwise, write the exact dashboard steps the user needs to take. 5. Verify recovery — After the fix, send a test email through the existing Webhook Pipeline Verifier, confirm the corresponding row appears within ~1 minute, and confirm the next scheduler tick computes . Relevant files - - - - - Volleyball Elite Academy Reply to this email — we read every reply. You received this because you have an account with Volleyball Elite Academy. elitevolleyball.training