Tim Jones
Tim Jones
The current implementation uses an internal queue with denouncing hard-coded to 60s. For per-second cron, this would need to be changed to 1s
The debounce I'm mentioning is to ensure 2 pgboss instances running cron monitoring can't create more than 1 job within the cron expression.
Please review the latest behavior in the v10 beta
I think it's generally accepted that most tasks should be able to completed in a finite amount of time, or you would lose the ability to monitor the process and...
I didn't realize you were reporting a bug. Ok, my best guess is that this exceeds a maximum integer value, since hours are converted into ms internally for the promise...
Maximum expiration was changed to 24 hours in v10
This is happening because the archive table doesn't have a primary key defined.
This is fixed in v10
Running start() will automatically run maintenance unless you've opted out of this. If so, you may want to create a dedicated function that runs on a cron and stays alive...