#Laravel friends, I need your help! I'm on a tight deadline and running into a weird issue where queued jobs are running even when the workers are stopped AND it's logging OLD exception verbiage instead of new. Details:
gist.github.com/chrispian/ea62ba268fbc790ef357a4f463d4f1cd
@martin_ro @HungryBus I ended up finding out that the network team cloned the box to create us a new dev env - so the queue worker was running over there causing the odd behavior we've been seeing. So glad to finally have found this!
Thank you guys both for trying to help. This was a tough one to prove out. Ended up watching DB connections because our network team didn't have a record of any clone being done - the ticket is still in progress! Such a weird one.
@martin_ro Thanks! Bad timing but I'm glad it happened, really learned a lot about the queue and debugging them even more and now I understand the serialization / deserialization even better. This was a good thing with horrible timing lol.
