Tim Jones
Tim Jones
Please try this again in 9.0.2 and see if it's resolved
This would be a good option to send(). You can use insert([jobs]) for now, however.
`send()` now supports an `{ id }` option in v10
You can pass in porsager's project via the `db` option in the constructor if you want. In terms of popularity, one of these is not like the other: 
How does the dependency on pg affect your usage?
Job queues don't typically offer job mutation features like this after they are created, because the queue system needs to have total control of its state to be reliable. Debouncing...
Internal maintenance guarantees active jobs are retried or failed after their timeout/expiration. This behaves similarly to the visibility timeout in SQS. You should tune the expiration to what should be...
I didn't mean to mark this as completed. I was resolving lot of old issues during the v10 release.
The scheduling section in the docs explains that minute-level precision is the minimum cron precision. Does this answer your question?
What if we cache the schedules once every 30s and then eval each second? It's a compromise that I think most would accept.