If your jobs call a third party API, sooner or later you will hit its rate limit and start getting 429 Too Many Requests. Hammering the API ha...

Your CRM integration goes down at nine in the morning. There are two thousand contact-sync jobs on the queue, and every one of them is now goi...

A few queue settings trip up nearly everyone, mostly because two of them look like they do the same thing and actually do not. Here is each on...

A third-party endpoint was down for twenty minutes overnight. It is back, and now there are four hundred rows sitting in failed_jobs. The work...

A job that creates shipping labels retries three times against a carrier API that is having a bad morning, then gives up. The row lands in fai...

You open your logs or failed_jobs table and find a job marked failed with MaxAttemptsExceededException and the message "Job has been atte...

A customer gets charged twice. Or the same shipping confirmation lands in their inbox three times. You read the job, and the logic is fine. It...

A support ticket lets people attach a screenshot, and you want the resizing done in the background. The obvious thing fails immediately: There...

For years the advice was clear: never run the database queue driver in production, use Redis. That advice is out of date. Modern databases fix...

This one fails immediately, in the request, before the job is ever queued: Others in the same family show up as Serialization of 'PDO' is not...

One of Horizon's nicest features is graceful shutdown: when told to stop, it waits for any in-flight jobs to finish before terminating its wor...

A job blows up in failed_jobs with a message like this: Listing 41 definitely existed when you dispatched the job. It does not exist now. Noth...

When you dispatch a job, it does not run there and then. It gets turned into a small record and stored, in MySQL, Redis, or SQS, until a worke...

Here is a common need. Every time a product is updated you dispatch a job to rebuild the search index. If ten products are edited in a minute,...

Once you have a queue running, everything starts to look like a job. Slow endpoint? Queue it. Sending an email? Queue it. Updating a counter?...

A database transaction groups several queries into one all or nothing unit. Either every query succeeds and the changes stick, or one of them...

You notice the same job ran twice. The email went out twice, the charge happened twice, and you are sure you dispatched it once. Before suspec...

You moved a slow thumbnail job onto the queue, deployed, and the endpoint is exactly as slow as it was before. There are no rows in the jobs t...

If your workers share a server with your web app, or run on a small box, they can quietly eat the resources your site needs. The goal is to le...

People love to argue about whether PHP is suited to long running processes. In practice, Laravel workers crunch enormous numbers of jobs relia...