Simon Tretter

This is already fixed in @hokify/agenda already since 2020 :-) see https://github.com/hokify/agenda/blob/1d75092b99c6128c2439921e95fe3171b0e5dec1/src/JobProcessor.ts#L457 you could try this fork instead

In @hokify/agenda only the relevant fields are updated after an exectuion, see https://github.com/hokify/agenda/blob/55d608e3cca48ec81dc4b7aaf142e4741c9fbd36/src/JobDbRepository.ts#L244 feel free to bring this changes over here or try to use the fork :-)

Hi @MikeShi42 , you are welcome :) Regarding your 2nd issue, what exactly do you mean with this? removing jobs before getting executed? or what do you mean by "marking...

@hokify/agenda 6.1.0 does this now https://github.com/hokify/agenda/commit/606e1413ec939d1e368db4a1af67c86d867b48d5 the more I was thinking about it, the more I was convinced to see this actually as a bug

check out https://github.com/hokify/agenda, which actually throws if a job exectuion takes too long

Interesting, are you doing using "failure" or "complete" hooks where you re-save / modify the agenda job object? What's your value for processEvery? Could it be that it is set...

Is the worker runnign over a year since the job has been queued the "first" time? To be honest, I guess it's a bug in the current version. I did...

I was thinking of a valid reason why this could happen, and I just stumpled upon following "issue" (which I had and was the reason for the fork in first...

I was thinking about this also, but I came up with an idea and just double checked it.. First: * jobProcessing only handles jobs that are already locked and are...

Hi all, I was looking into this out of curiosity. Am I right that the main use case for this is that a job's database queries are then handled by...