Here's yet another example of how I got burned when my local dev environment didn't match my prod environment. Sync queues work differently than other queue types.
masteringlaravel.io/daily/2024-08-06-sync-queue-works-differently-than-async
Back
•
In response to @sinnbeck
The test as originally written was passing because the queue was running synchronously.
The solution involved capturing the change state as a separate job param and passing it along with the model. This approach no longer relied on the change state being in memory when the job was processed.