Open Arsca opened 10 years ago
You're right about using cb('wait')
- as noted at http://kusor.github.io/node-workflow/#using-tasks-to-re-queue-retry-or-put-jobs-to-wait - that's definitely an issue with the redid backend. I'll take a look, thanks!
Hi,
I have been trying to figure out how to put a job on hold and resume it later. The documentation is not so clear on the subject matter. So far, if I understand correctly, during the execution in the task body I should call cb('wait') to put it on hold and the external system can resume it by calling the REST api at '/jobs/jobUuid/resume' . So far I have not managed to do it.
If I use the cb('wait') signal for callback I get the Redis backend error:
Would be nice to see an example how to do it.
kind regards,