Not running again
See original GitHub issueWhy does it say not running again? How to debug this?
{"line":"63","file":"synced-cron-server.js","message":"SyncedCron: Scheduled \"Sample name\" next run @Sat Sep 10 2016 03:00:00 GMT+0000 (UTC)","time":{"$date":1473476294724},"level":"info"}
{"line":"63","file":"synced-cron-server.js","message":"SyncedCron: Not running \"Sample name\" again.","time":{"$date":1473476400020},"level":"info"}
SyncedCron.config({
log: true
});
SyncedCron.add({
name: 'Sample name',
schedule: function(parser) {
return parser.recur().on(0).minute(); // 0th minute of every hour
},
job: function() {
// do the job
}
});
// Start all cron jobs
SyncedCron.start();
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
List of U.S. Congress incumbents who did not run for re ...
Of those, 38 members—six senators and 32 representatives—announced their retirement. Five retiring Senate members were Republicans and one was a Democrat, and ...
Read more >What if Biden does not run again? - Reuters
The U.S. midterm elections on Tuesday will do much more than shape the next two years of Joe Biden's presidency.
Read more >Majority of Americans don't want Biden or Trump to run again ...
That's how majorities of the public responded when the CNBC All-America Economic Survey asked if President Joe Biden or former President Donald ...
Read more >Members of Congress not running for reelection in 2022
Dozens of lawmakers have announced they won't seek reelection in 2022, in what's expected to be a tough year for Democrats trying to...
Read more >Dozens of lawmakers not seeking re-election in 2022 - NY1
Ahead of the crucial 2022 midterm elections, nearly 50 members of the House of Representatives have said they are not seeking re-election.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@FlawaCLV you’re running SyncedCron on more then one server, but all servers connect to the same database. Every time one SyncedCron instance on one server runs a task, it marks it as ran in the cronHistory db collection, and all the other servers running SyncedCron instances will tell you they’re not running the task again, because it’s already been run.
In short, it’s not an issue. It’s normal behaviour unless you run your meteor app on only one server.
@TheGame2500 thanks for your answer. Indeed, I found that yesterday. We’re 3 developers running our servers locally but hitting the same MLAB database. We solved it by reconfiguring a little bit are environnement.