Supabase edge cron is deployed, but production is drifting
Confirm every scheduled function run with completion pings and alerting.
When scheduled edge functions degrade, data sync and cleanup tasks quietly fall behind.
- Silent misses create stale product data
- Edge logs are reactive, not proactive
- No simple heartbeat per critical function
Step 1
Attach success/fail ping calls to each function run
Step 2
Tune expected interval and grace windows
Step 3
Use alerts to catch drift before customers do
Supabase function ping
await fetch('https://silentfail.dev/api/ping/YOUR_TOKEN/success', {
method: 'POST'
});Built for developers. No credit card. Free for 1 check.
Lightweight ping API for cron, queue, and serverless runtimes.
Alerting channels: email + Slack, with event history for audits.
Public status available at /status.
Does this require Supabase extension setup?
No extra extension is required.
Can I track function failures?
Yes, call the fail endpoint on error paths.
Can I share one token?
Prefer one token per function for clear ownership.
Can I monitor latency?
Include duration metadata on your ping requests.
Will this work for manual triggers too?
Yes, any invocation can send pings.