I have two aws servers, identical setup: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic uname -r 4.15.0-1035-aws node --version v8.16.0 cat package.json | grep cron "cron": "^1.7.1",

both have cron running with this code: new CronJob('*/10 * * * * *', procNewBlock, null, true, 'Europe/Berlin');

both stopped running at approximately the same time, the first was running the last time at: May 2 09:05:47 UTC

the second last run was at: May 2 09:06:30 UTC

so far this was the only time that this happend (running for about 1 month now). To me it looks as if some scheduled system task outside of nodejs is killing the crons. But any help greatly appreciated. The nodejs processes did not see any interruption.

@awaismehmood88 I'm trying to reproduce your issue. what does the findJob function do? I use this library for processes that run for months without stopping so it must only happen under specific circumstances