Workers cron trigger fired. Did your job actually finish?
Add explicit completion pings to stop guessing about background reliability.
Edge schedules can execute yet still fail due to upstream APIs, limits, or bad deploys.
- Trigger execution does not guarantee business success
- Edge failures are hard to surface in one place
- Missing heartbeats go unnoticed until users report issues
Step 1
Instrument cron handler with success/fail pings
Step 2
Set expected intervals aligned to trigger schedule
Step 3
Respond quickly through alert channels
Workers scheduled handler
export default {
async scheduled() {
try {
await runEdgeTask();
await fetch('https://silentfail.dev/api/ping/YOUR_TOKEN/success', { method: 'POST' });
} catch (e) {
await fetch('https://silentfail.dev/api/ping/YOUR_TOKEN/fail', { method: 'POST' });
throw e;
}
}
};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.
Can I use this with wrangler cron?
Yes, any scheduled worker can ping endpoints.
Does this add high latency?
No, one lightweight HTTP request per run.
Can I test locally?
Yes, call the ping URL manually with curl.
Can we separate environments?
Use distinct tokens per env and job.
Does this support failover alerts?
Alerts fire when expected success is absent or failure is explicit.