Running Laravel jobs with deleted models

If you try to dispatch a job with a model just after it was deleted, you will encounter a small problem:

Fortunately, there’s a quick fix for that — just remove SerializesModels trait from the job class. The trait causes the job to retrieve the model instance from database when it is being processed in the queue. This is a prefered behaviour in many cases, but not this one.

Without this trait the whole instance is serialized when dispatching and restored without database involvement when processing in the queue, which is exactly what we want.

This might also serve as optimization technique, saving you some database queries.

P.S. There’s no such problem when processing soft-deleted items, as models are still in the database when processing the queue.

Related posts:

As the skill sets across a design team grow in breadth and depth, it is integral that the team shares valuable knowledge across the team. This begins with the understanding that the domain expertise…

You know just in a case I had to thank someone, and I don’t wanna forget nobody, so Let’s do this fast, first off all the foreign associated press thanks for having me here,I don’t know who or what…

Search engine optimization (SEO) is an important part of online marketing. It helps businesses increase their visibility on search engines, such as Google. But, what if you want to gain visibility…