One production problem I traced wasn't a bug in one line. It was a request that waited on service A, which waited on B, which waited on a slow C, until everything timed out. The fix was to do only the required action synchronously and move the rest to queues.
So when a Laravel release changes queues, the question I care about is: does this make queue behaviour easier or harder to review?
Laravel 13 (released March 17, 2026, PHP 8.3+) adds a few features that move queue policy next to the code. This is a review of what the official 13.x docs say, plus the traps I'd check for in code review. It is not a report from a production migration.
1. Queue::route : one place for where jobs run
Before, the queue and connection for a job were often decided at each dispatch site ( ->onQueue('video') ) or in properties on the job.…