Processing items synchronously about agenda HOT 1 CLOSED

Not calling done would still allow multiple jobs to be run at once, specifically on per-job concurrency, or entire queue concurrency. A job will be considered "finished" when you call done(). If you do not take done as an argument, then it will be marked as done when the function reaches the end. You shouldn't take done as an argument if you aren't going to call it, as then agenda will

If you want agenda to only ever run one job at a time, you can do the following:

agenda.maxConcurrency(1);

This tells agenda to only ever allow one job to be processing at once.

If you want to specify it for a specific job, you can do:

agenda.define('some job', {concurrency: 1}, function(job, done) {
});

So, for example:

agenda.maxConcurrency(3);

var start = new Date();

agenda.define('longer job', {}, function(job, done) {
   setTimeout(function() {
      var now = new Date();
      console.log("Hello one - %d ms later", now - start);
      done();
   }, 1700);
});

agenda.define('long job', {concurrency: 1}, function(job, done) {
   setTimeout(function() {
      var now = new Date();
      console.log("Hello two - %d ms later", now - start);
      done();
   }, 1000);
});

agenda.now('longer job');
agenda.now('longer job');
agenda.now('long job');
agenda.now('long job');
agenda.now('longer job');
agenda.start();

Results in the following:

Hello two - 1026 ms later
Hello one - 1724 ms later
Hello one - 1725 ms later
Hello two - 2028 ms later
Hello one - 3425 ms later

As for the callback signature:

job is a Job instance. See here for documentation.

done is a function which lets the agenda know that the job finished, and tells it to queue up the next job, given the current state of running jobs and concurrency limitations.

Hope this helps

from agenda.