Laravel Queue Retry Strategies & Dead-Letter Patterns | Mohamed Said [Skip to content](#main) [ ![](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed SaidLaravel Backend Engineer ](https://www.msaied.com/public) - [Home](https://www.msaied.com/public) - [Projects](https://www.msaied.com/public/projects) - [Articles](https://www.msaied.com/public/articles) - [Certificates](https://www.msaied.com/public/certificates) - [About](https://www.msaied.com/public#about) [ Contact](https://www.msaied.com/public#contact) Menu Menu ---- Close - [HomeStart here](https://www.msaied.com/public) - [ProjectsCase studies](https://www.msaied.com/public/projects) - [ArticlesEngineering notes](https://www.msaied.com/public/articles) - [CertificatesCredentials](https://www.msaied.com/public/certificates) - [AboutHow I work](https://www.msaied.com/public#about) - [ContactGet in touch](https://www.msaied.com/public#contact) [Start a conversation](https://www.msaied.com/public#contact) [WhatsApp](https://wa.me/201094619204) [Email](mailto:hello@msaied.com) 1. [Home](https://www.msaied.com/public) 2. / 3. [Articles](https://www.msaied.com/public/articles) 4. / 5. Laravel Queues: Reliable Job Retry Strategies with Exponential Backoff and Dead-Letter Handling Laravel Queues: Reliable Job Retry Strategies with Exponential Backoff and Dead-Letter Handling ================================================================================================ Beyond basic retries: how to implement exponential backoff, custom retry delays, and dead-letter queue patterns in Laravel to make async jobs genuinely resilient in production. ![](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) [Mohamed Said](https://www.msaied.com/public#person) Published 10 Jul 2026 · Updated 10 Jul 2026 · 4 min read ShareCopy linkCopied ![Laravel Queues: Reliable Job Retry Strategies with Exponential Backoff and Dead-Letter Handling](https://cdn.msaied.com/407/704b143d40e1a6ac5a2faa4efb900174.png) On this page +1. [Why Default Retry Behaviour Isn't Enough](#why-default-retry-behaviour-isnt-enough) 2. [Exponential Backoff with Jitter](#exponential-backoff-with-jitter) 3. [Per-Exception Retry Logic](#per-exception-retry-logic) 4. [Dead-Letter Queue Pattern](#dead-letter-queue-pattern) 5. [Step 1 — Custom Failed Job Handler](#step-1-custom-failed-job-handler) 6. [Step 2 — Replay Command](#step-2-replay-command) 7. [$maxExceptions vs $tries](#codemaxexceptionscode-vs-codetriescode) 8. [Key Takeaways](#key-takeaways) Why Default Retry Behaviour Isn't Enough ---------------------------------------- Laravel's queue system ships with `$tries` and `$backoff` on every job. Most teams set `$tries = 3` and call it done. That works until you hit a flaky third-party API, a brief database overload, or a downstream service that needs 30 seconds to recover — not 3 seconds. This article covers three concrete improvements: exponential backoff with jitter, per-exception retry logic, and a dead-letter pattern that keeps failed jobs observable and replayable. --- Exponential Backoff with Jitter ------------------------------- A flat `$backoff = 5` means every retry hammers the same resource at the same cadence. Exponential backoff spreads load; jitter prevents the thundering-herd problem when many jobs fail simultaneously. ```php class SyncOrderToWarehouse implements ShouldQueue { use Dispatchable, InteractsWithQueue, Queueable, SerializesModels; public int $tries = 6; public int $maxExceptions = 3; // Called by Laravel to determine delay before each attempt. public function backoff(): array { return [ $this->jitter(10), // attempt 2: ~10s $this->jitter(30), // attempt 3: ~30s $this->jitter(60), // attempt 4: ~60s $this->jitter(120), // attempt 5: ~120s $this->jitter(300), // attempt 6: ~300s ]; } private function jitter(int $base): int { return $base + random_int(0, (int) ($base * 0.2)); } public function handle(WarehouseClient $client): void { $client->sync($this->order); } } ``` Returning an **array** from `backoff()` maps each value to the corresponding retry attempt. Laravel falls back to the last value for any remaining attempts beyond the array length. --- Per-Exception Retry Logic ------------------------- Not all exceptions are equal. A `RateLimitException` deserves a long wait; a `ValidationException` should fail immediately without retrying at all. ```php public function handle(WarehouseClient $client): void { try { $client->sync($this->order); } catch (RateLimitException $e) { // Re-release with a specific delay, not the backoff schedule. $this->release($e->retryAfter()); } catch (\InvalidArgumentException $e) { // Permanent failure — don't retry, go straight to failed table. $this->fail($e); } } ``` `$this->release(int $delay)` puts the job back on the queue with a custom delay without consuming a retry attempt. `$this->fail(Throwable $e)` marks the job failed immediately, bypassing remaining tries. --- Dead-Letter Queue Pattern ------------------------- Laravel's `failed_jobs` table is a dead-letter store, but it's passive. A production system needs active monitoring and a replay path. ### Step 1 — Custom Failed Job Handler Register a callback in `AppServiceProvider`: ```php Queue::failing(function (JobFailed $event) { Log::critical('Job permanently failed', [ 'job' => $event->job->getName(), 'connection' => $event->connectionName, 'queue' => $event->job->getQueue(), 'payload' => $event->job->payload(), 'exception' => $event->exception->getMessage(), ]); // Optionally push to a dedicated dead-letter queue for inspection. dispatch(new DeadLetterJob($event->job->payload())) ->onQueue('dead-letter'); }); ``` ### Step 2 — Replay Command ```php class ReplayDeadLetterCommand extends Command { protected $signature = 'queue:replay-dead-letter {--limit=50}'; public function handle(): void { DB::table('failed_jobs') ->latest() ->limit((int) $this->option('limit')) ->get() ->each(function (object $row) { Artisan::call('queue:retry', ['id' => [$row->uuid]]); $this->line("Retried: {$row->uuid}"); }); } } ``` Pair this with a Filament resource over `failed_jobs` for a UI-driven replay workflow. --- `$maxExceptions` vs `$tries` ---------------------------- These two properties are frequently confused: | Property | Meaning | |---|---| | `$tries` | Maximum total attempts (including first run) | | `$maxExceptions` | Max *unhandled* exceptions before marking failed, regardless of `$tries` | Set `$maxExceptions` lower than `$tries` when you use `$this->release()` manually — otherwise a job that keeps rate-limiting itself will never count those releases against `$tries`, but unhandled exceptions will still accumulate. --- Key Takeaways ------------- - Return an **array** from `backoff()` to define per-attempt delays; add jitter to avoid thundering herds. - Use `$this->release($delay)` for recoverable waits and `$this->fail($e)` for permanent errors — both bypass the default backoff schedule. - `$maxExceptions` caps unhandled exceptions independently of `$tries`; understand the distinction before combining them. - A `Queue::failing()` callback turns the passive `failed_jobs` table into an active alerting and dead-letter pipeline. - A replay command over `failed_jobs` gives you a safe, auditable path back to production queues. - [laravel](https://www.msaied.com/public/articles?search=laravel) - [queues](https://www.msaied.com/public/articles?search=queues) - [reliability](https://www.msaied.com/public/articles?search=reliability) - [backend](https://www.msaied.com/public/articles?search=backend) Frequently asked questions --------------------------- What is the difference between $tries and $maxExceptions on a Laravel job?$tries is the total number of attempts Laravel will make, including the first run. $maxExceptions counts only unhandled exceptions; calls to $this->release() do not increment it. A job can be released many times without consuming $maxExceptions, but each unhandled throw does. Does adding jitter to backoff() actually help in production?Yes. When a downstream service fails, many queued jobs often fail at the same moment. Without jitter, all retries fire at identical intervals, recreating the same spike. Adding a small random offset (10–20% of the base delay) spreads retries across time and reduces the chance of overloading the recovering service again. How do I prevent a job from retrying on a specific exception type?Catch the exception inside handle() and call $this->fail($exception). This marks the job as permanently failed immediately, skipping all remaining retry attempts and backoff delays, and records it in the failed\_jobs table. ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp)About the author ---------------- [Mohamed Said](https://www.msaied.com/public#person)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. [About](https://www.msaied.com/public#about) [GitHub ↗](https://github.com/EG-Mohamed) [LinkedIn ↗](https://www.linkedin.com/in/msaiedm/) [WhatsApp ↗](https://wa.me/201094619204) [Email Address ↗](mailto:hello@msaied.com) [My CV ↗](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view) [Previous articleFilament v3 Custom Table Columns: Rendering, State, and Performance at Scale](https://www.msaied.com/public/articles/filament-v3-custom-table-columns-rendering-state-and-performance-at-scale) [Next articleLaravel Enum Casts, Backed Enums, and Value Semantics in PHP 8.3](https://www.msaied.com/public/articles/laravel-enum-casts-backed-enums-and-value-semantics-in-php-83) On this page ------------- 1. [Why Default Retry Behaviour Isn't Enough](#why-default-retry-behaviour-isnt-enough) 2. [Exponential Backoff with Jitter](#exponential-backoff-with-jitter) 3. [Per-Exception Retry Logic](#per-exception-retry-logic) 4. [Dead-Letter Queue Pattern](#dead-letter-queue-pattern) 5. [Step 1 — Custom Failed Job Handler](#step-1-custom-failed-job-handler) 6. [Step 2 — Replay Command](#step-2-replay-command) 7. [$maxExceptions vs $tries](#codemaxexceptionscode-vs-codetriescode) 8. [Key Takeaways](#key-takeaways) ### Have a technical challenge? Tell me what you’re building. I reply within two working days. [Start a conversation](https://www.msaied.com/public#contact) Related articles ----------------- [ ![](https://cdn.msaied.com/740/cce86edc21eddcbdd2f2454fadaf9c70.png) · 3 min read### The Pipeline Pattern in Laravel: Custom Pipelines Beyond Middleware 5 Oct 2026 ](https://www.msaied.com/public/articles/the-pipeline-pattern-in-laravel-custom-pipelines-beyond-middleware-1) [ ![](https://cdn.msaied.com/739/2d6897fdcdcf090613f96f72a64b8a78.png) · 4 min read### MySQL Full-Text Search in Laravel: Indexes, Relevance Scoring, and Boolean Mode 4 Oct 2026 ](https://www.msaied.com/public/articles/mysql-full-text-search-in-laravel-indexes-relevance-scoring-and-boolean-mode) [ ![](https://cdn.msaied.com/738/073696a3fefe18bec825beec5ac658f5.png) · 4 min read### Laravel Queue Rate-Limited Middleware: Throttling Jobs Without Losing Work 4 Oct 2026 ](https://www.msaied.com/public/articles/laravel-queue-rate-limited-middleware-throttling-jobs-without-losing-work) Have a technical challenge? ---------------------------- Tell me what you’re building. I reply within two working days. [Discuss your project ↗](https://www.msaied.com/public#contact) © 2026 Mohamed Said · Built with Laravel, meant to last.Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. - [Home](https://www.msaied.com/public) - [Articles](https://www.msaied.com/public/articles) - [Certificates](https://www.msaied.com/public/certificates) - [GitHub](https://github.com/EG-Mohamed) - [LinkedIn](https://www.linkedin.com/in/msaiedm/) - [WhatsApp](https://wa.me/201094619204) - [Email Address](mailto:hello@msaied.com) - [My CV](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view) - [Sitemap](https://www.msaied.com/public/sitemap.xml)