Saving job's start date as last run to avoid progressive shifting of the scheduler?

[SebC99]

Hello @flovilmart
I've tried to use your parse job runner, but I've noticed a "shift": I have a job which is supposed to run once a day at 6pm UTC, but it runs progressively later...
Reason is that as it checks for lastRun and that this lastRun is set to the "end of job", there's a progressive shift because of the duration of the job itself.

Worse, if you configure the runner to run only once per hour for example, and if it misses the lastRun by one second, you will have a one hour shift in the schedule.

Is it on purpose?

[SebC99]

My mistake, it seems you save the starting date, so then I don't know what causes the shift...

[flovilmart]

we have it scheduled to run every minutes, it should run at an interval smaller than your schedule.

The lastRun should be set on the date the job running has run (https://github.com/AmpMe/parse-server-job-runner/blob/master/lib/JobSchedule.js#L63) not when it finished running. That's on purpose as well. The Jobs endpoint always respond without waiting for the job to be completed.

I recommend you run it in a more periodical manner to avoid those shifts.

[SebC99]

I guess it's because we're using AWS Lambda to run the scheduler: it needs a few milliseconds/seconds to start the runner, so the date passed to the run method is not exactly the starting date of the process, which could mess up with the delay between jobs.
I'll try running it every minutes to see if it's better
Thanks :)