Hi @IbnJubayr, I am sorry to hear you’re having trouble. Can you confirm whether this issue persists with the latest version of n8n (0.208.0)? If so, can you share details on how to create an execution that has this problem?
Hi @MutedJam - sorry for the delay in replying, i’ve been away.
Unfortunately I cannot pinpoint what is causing this, but i’ve also noticed another issue now. My workers are no longer processing cron jobs and when I took a deeper look, i found this error in the container logs
redis parser user_script:81: too many results to unpack.
Thanks @krynble - is there any documentation I can read regarding how queue mode works in detail? Why was there that many active jobs in the list? Did something go wrong and everything stopped processing?
To resolve the issue, I had to delete the active key so that jobs could start getting processed again
As suggested in the link you’ve sent, this is an issue with the underlying LUA script used by the bull system when there were more than 8k active items; it was having issues parsing those.
This can happen if your workers go offline for a while and you have too many jobs piling up and reaching over 8k items in queue.
We have an internal ticket to update the Bull queue system to prevent this issue in the future.