Brian Woodward

This was not designed to be horizontally scaled since there is a possibility that a job could be picked up by multiple servers. I think this can be implemented though...

I can think of 2 different approaches to this: - Update this library to have a flag on the job to only run once and create a new job for...

@haynzz that would be a good idea, however I'm using the [cron](https://github.com/ncb000gt/node-cron) library which it looks like it doesn't support years. That library links to this [cron tab documentation](http://crontab.org/).

You're correct that there are no differences between `addJob` and `updateJob`. I had stubbed out the methods for the api before implementing them and didn't really see how they could...

You can get a job by name with [.getJob](https://github.com/doowb/firebase-cron#getjob). This will have the `nextRun` timestamp: ```js cron.getJob('test', function(err, job) { if(err) return console.error(err); console.log(new Date(job.nextRun)); }); ``` You can remove...

Ah... for knowing if a job is currently running, then you'd have to look at the `firebase-queue` stats (this isn't something built into `firebase-cron`. `cron.run` returns a function that will...

> But how to know the status by watching the firebase-queue, See the [firebase-queue](https://github.com/firebase/firebase-queue) documentation. It's something that you'll have to add to your code. `firebase-cron` only takes data and...

Not in this case, because `patterns.splice(1, i)` is removing an item, then the `i++` in the for loop effectively skips the next item in the patterns array. Adding the `i--`...

Can you provide some example code with a case where this is causing a bug? If so, a PR with a fix for the bug will be welcome.

Can you provide some example code with a case where this is causing a bug? If so, a PR with a fix for the bug will be welcome.