title: firebase-queue: Multiple workers not running correctly?
body: <p>I'm pretty new to Node.js, though I've been writing javascript for years. I'm more than open to any node advice for best-practices that I'm not following, or other rethinks. That said:</p>
  
  <p>I'm building a system in which a user creates a reservation, and simultaneously submits a task for my firebase-queue to pick up. This queue has multiple specs associated with it. In turn, it's supposed to:</p>
  
  <ol>
  <li>check availability, and in response confirm/throw an alert on the reservation and update the firebase data accordingly.</li>
  <li>Update the users reservations, which is an index of reservation object keys, and removing any redundant ones.</li>
  <li>Use node-schedule to create dated functions to send notifications about the pending expiration of their reservation.</li>
  </ol>
  
  <p>However, when I run my script, only one of the firebase-queues that I instantiate runs. I can look in the dashboard and see that the progress is at 100, the _state is the new finished_state (which is the next spec's start_state), but that next queue won't pick up the task and process it.</p>
  
  <p>If I quit my script and rerun it, that next queue will work fine. And then the queue after that won't work, until I repeat the act of quitting and rerunning the script. I can continue this until the entire task sequence completes, so I don't think the specs or the code being executed itself are blocking. I don't see any error states spring up, anyway.</p>
  
  <p>From the documentation it looks like I should be able to write the script this way, with multiple calls to 'new Queue(queueRef, options, function(data, progress, resolve, reject)...' and they'll just run each task as I set them in their options (all of which are basically:</p>
  
  <pre><code>var options = {
    'specId': 'process_reservation',
    'numWorkers': 5,
    'sanitize': true,
    'suppressStack': false
  };
  </code></pre>
  
  <p>but, nope. I guess I can spawn child-processes for each of the queue instances, but I'm not sure if that's an extreme reaction to the issues I'm seeing, and I'm not sure if it would complicate the node structure in terms of shared module exports. Also, I'm not sure if it'll start eating into my concurrent connection count.</p>
  
  <p>Thanks!</p>