TL;DR A job dispatched once, at row-creation time, has a silent failure mode: if that...
TL;DR
A job dispatched once, at row-creation time, has a silent failure mode: if that dispatch is lost, the row sits pending forever — and never appears in failed_jobs.
Retries only exist for jobs that ran. A job that never entered the queue has nothing to retry.
Fix: a reconciler — a scheduled sweep for stale, unclaimed rows that re-dispatches them. The database is the source of truth; the queue is just delivery.
The bug that leaves no trace
Job 4817 was submitted exactly once, and it produced three emails, two database rows, and one very...
A scheduled job has two failure modes. The loud one throws an error and your alerting catches it. The...
hat "rare" bug that looks intermittent but is actually deterministic. It is just waiting for your...
Cómo funcionan las colas de trabajo por dentro: reintentos con backoff, idempotencia para evitar duplicados, dead-letter queues y…
My previous piece, "Making a launchd Job Unload Itself," built a job that runs exactly once and then...
You're sending an email. The SMTP server hiccups. Your code throws. The email never sends. Nobody...
