startedAt is one second earlier then intendedAt

[artpolikarpov]

How is this possible that job is starting few ms earlier?

{
  "_id": "9pb3uncdsyXQ3PbZN",
  "intendedAt": new Date("2016-09-05T13:20:00+0300"),
  "name": "operating-hours",
  "startedAt": new Date("2016-09-05T13:19:59+0300"),
  "finishedAt": new Date("2016-09-05T13:20:00+0300"),
  "result": null
}

[33Fraise33]

We're seeing the same issue but having a much greater difference.

{ 
    "_id" : "WtS9Ppf5RZL5sFcaM", 
    "intendedAt" : ISODate("2017-04-22T17:30:00.000+0000"), 
    "name" : "Open checkin for Hearthstone 1v1 Cup (id: Kf5DFKNqZaCpXiq9A)", 
    "startedAt" : ISODate("2017-04-22T17:29:27.696+0000"), 
    "finishedAt" : ISODate("2017-04-22T17:29:29.453+0000"), 
    "result" : null
}

I have cronjobs starting up to 1 minute before they were intended to run. Is there an option to have the cronjobs run no any sooner than the intendedAt? Later wouldn't be so bad but sooner is kind of a big problem.

If you have already found a solution @artpolikarpov let me know ;)

[tomtom87]

Can you guys please try setting the cron to start 1 minute later, this seems to be a bug in the timing so as a workable way to use it just append 1 minute to when you wish to begin this is how I am getting around it... hope this can help