Open tmoens opened 6 years ago
You're not missing anything obvious, the problem is that the save callback is never called on success but the job is created asynchronously. There's no way to know when the job has actually been created. Which seems like a major oversight in the API design.
Hi,
Any changes on this? I need to keep track of my job ids in case i need to cancel them (programatically) in the future, and this complicates a lot
Thank you very much
I have a simple node.js server. It supports the ocassional HTTP request to myserver/goDoSomethingThatTakesAWhile
I want to kue the job and pass back the job Id in the HTTP response and then let the client go wild checking for progress.
My problem is that the function that does the save and and wants to return the ID completes before the save completes and I do not get the job Id to send to the client.
I suspect I am missing something terribly obvious here.