-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot do job.update when job runs in separate process #1279
Comments
hi @manast , thanks |
It is a missing feature. It needs to be implemented I am have a lot on my table right now so I cannot do an ETA right now. |
Any update ? |
+1 :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
🎉 This issue has been resolved in version 3.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
I have changed the queue processor from a normal process to a separate process and now I cannot update a job anymore.
It throws the following error:
(node:7068) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: job.update is not a function
Minimal, Working Test code to reproduce the issue.
when I convert the processor call to a separate process the
job.update
throws the errorBull version
3.4.8
Additional information
This is the content of job when processor is within the master process:
This is the content of job when job runs in a separate process:
It seems that when the job is in a separate process some properties are missing.
The text was updated successfully, but these errors were encountered: