{
  "id": 11219661,
  "title": "Slow Jobs, Killer Containers: Laravel Queue Timeouts and Crashes in Docker",
  "url": "https://urgent.news/2026/10/01/slow-jobs-killer-containers-laravel-queue-timeouts-and-crashes-in",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-01T15:14:06.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/gabbrowick/slow-jobs-killer-containers-laravel-queue-timeouts-and-crashes-in-docker-204g"
  },
  "original_language": "en",
  "account": "In the world of Laravel, jobs can fail in three different ways when executed within Docker containers: worker timeout, kernel memory limit, and deploy pull. Laravel 13.33 and 13.34 have addressed two of these issues, but one remains reliant on user intervention. When a job exceeds its timeout, Laravel previously killed the worker using SIGKILL. However, Laravel 13.34 now records the timeout as an exception when $failOnTimeout is set, allowing the job to retry and be counted towards the $maxExceptions limit. Additionally, Laravel 13.33 introduced a static flag, $killOnTimeout, which when set to false, allows the worker to survive a timeout, catching the TimeoutExceededException and continuing to the next job. This change provides a more graceful handling of timeouts, allowing jobs to clean up resources and continue processing without requiring the framework to restart.",
  "summary": "A job that sends an email takes half a second. A job that calls a generative model takes as long as the provider feels like, and sometimes a lot longer. Run that job in a Docker container and it has three ways to die: the worker timeout fires, the kernel kills it for memory, or a deploy pulls the container out from under it. Until this month Laravel treated those three deaths differently and…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}