BullMQ worker is up, but jobs are silently stuck
Monitor each critical queue execution path with explicit success and fail pings.
Queue processors can stall after deploys, deadlocks, or redis turbulence while dashboards still look alive.
- Queue backlog grows before anyone notices
- Workers can crash between logs and dashboards
- Business tasks fail with delayed detection
Step 1
Wrap queue handlers with start/success/fail pings
Step 2
Set expected intervals for key high-frequency jobs
Step 3
Alert on missing pings to catch worker stalls
BullMQ processor ping
worker.process(async (job) => {
try {
await runJob(job);
await fetch('https://silentfail.dev/api/ping/YOUR_TOKEN/success', { method: 'POST' });
} catch (error) {
await fetch('https://silentfail.dev/api/ping/YOUR_TOKEN/fail', { method: 'POST' });
throw error;
}
});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.
Is this a replacement for Bull Board?
No, it adds proactive heartbeat alerting.
Can I monitor per queue?
Yes, create one check per critical queue.
Can I include metadata?
Yes, pass optional message and duration query params.
Will retries spam alerts?
Tune expected intervals and send fail only on terminal failures.
Can I start free?
Yes, free tier supports a first monitored check.