You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there,
Thanks for the amazing library!
I'm wondering if it is possible to communicate with a job after it was created.
In my specific example merely changing the data property would be sufficient.
I found out how to do it, but the change of the job is not reflected in the worker (I use clustering).
Job.get(rId, (err, job) => {
if (job) {
(job.data as QueueRenderPayloadData).shouldStop = true
}
})
I also tried to emit function:
Job.get(rId, (err, job) => {
if (job) {
const emitWorked = job.emit('customevent', { stop: true })
}
})
But emitWorked is always false, is there something to keep in mind when using clustering and emitting?
Thanks for your help!
The text was updated successfully, but these errors were encountered:
Hey there,
Thanks for the amazing library!
I'm wondering if it is possible to communicate with a job after it was created.
In my specific example merely changing the data property would be sufficient.
I found out how to do it, but the change of the job is not reflected in the worker (I use clustering).
I also tried to emit function:
Job.get(rId, (err, job) => {
if (job) {
const emitWorked = job.emit('customevent', { stop: true })
}
})
But emitWorked is always false, is there something to keep in mind when using clustering and emitting?
Thanks for your help!
The text was updated successfully, but these errors were encountered: