I might be doing something wrong here, but I'm running into an issue where, if the Laravel queue is set to use Beanstalk, job exceptions are not handled correctly.
The crux of the issue appears to be that once the job fails, it disappears from Beanstalk.
So when the DefaultEventManager class tries to call $event->job->attempts() (which gets forwarded to the queue connection), it fails.
I might be doing something wrong here, but I'm running into an issue where, if the Laravel queue is set to use Beanstalk, job exceptions are not handled correctly.
The crux of the issue appears to be that once the job fails, it disappears from Beanstalk. So when the DefaultEventManager class tries to call $event->job->attempts() (which gets forwarded to the queue connection), it fails.
Full stacktrace