Replies: 3 comments 2 replies
-
So it looks like you have a lot of active jobs that do not complete. This is normally a bug in the processor code where the jobs are just being processed for-ever, this can be for multiple reasons, like not returning a promise that resolves, etc. |
Beta Was this translation helpful? Give feedback.
-
Thanks or your answer @manast . This was my best guess also. Maybe you can take a look at my code? This is what my job looks like:
Something else is noteworthy here: I'm calling two API's. One where I don't get much errors and one which fails occasionally. If it fails, my jobs move to the Delayed state and get processed again, which is fine. But this is the one that gets stuck over time. Is there a thing as "too much errors"? 😅 As for the QueueScheduler, thats the only thing I'm doing with it:
Do I need to do something else? |
Beta Was this translation helpful? Give feedback.
-
First of all you do not need to wrap the code in a try/catch, thats what the job processor does for you and fail the job accordingly. Secondly, this call |
Beta Was this translation helpful? Give feedback.
-
I have a expressJS server where I use queues to make API calls and store the data I receive in a database. I usually add 10000 - 15000 jobs. All works great until it doesn't. After 1000 - 3000 jobs the queue just stop working.
I don't get an error or anything.
This is what the Dashboard currently looks like. Does anyone have an idea why this is happening or how I can debug this?
Beta Was this translation helpful? Give feedback.
All reactions