Juan Lago

There another possible reason that keep some jobs stuck on running and is when jobs are distributed across multiple Laravel workers on different servers (distributed system). See https://github.com/romanzipp/Laravel-Queue-Monitor/pull/68 for more...

@romanzipp : Hey Roman, Do you think that is feasible to merge this pull request?

Hi Roman. I am currently running two servers as queue workers that are connected to the same queue. I also use a Redis server as cache driver that support locks....

I have to say that I have 1 or 2 jobs every day that keep stuck on running state every day. Those jobs stuck jobs are diverse and I run...

I enclose another screenshot of another job duplicate.  As you can observe the oldest job dispatched is the job that was executed, and the first one was totally ignore...

I can see that this issue is still present in the current version. I requested to pull a new test case. I enclose a raw test where the linear Ad...

For some Ads providers is quite important to inject cookies to users. They use the cookies for metrics and retargeting purposes. The only issue using "withCredentials" is that XMLHttpRequest will...

@jonhoo : Regarding to the "onFinish" event, I think that is quite important, The reason is that sometimes the Ad provider send empty VAST documents (without linear and non-linear ads),...

I think that to use onFetched also as onFinish is also a fair solution, so for example if Ad is not retrieved the onFetched callback can return "null".

Hi Dries, I can reproduce with 9.30, however I was doing some research and I think I found the reason. It seems that my cache.php config file has missing the...