5

I know there's job.next_run_time to get the next run, but anyway to calculate what would have been the previous run time?

Romey-Rome
  • 91
  • 1
  • 8
  • Maybe the job itself can write somewhere when it was run? – Mikko Ohtamaa Jul 22 '15 at 21:54
  • That would work if I was using it as intended, but I'm only using the parser part of it to parse out quartz cron schedule from another system. – Romey-Rome Jul 22 '15 at 22:11
  • You lost me. Can you please add some code to the question, so we get more context what you are trying to do. – Mikko Ohtamaa Jul 22 '15 at 22:17
  • @MikkoOhtamaa A bit late to the party but I think he means he's using APScheduler for cron syntax parsing only, and not for its actual scheduler. I'm looking at a similar need now and will be looking at https://github.com/josiahcarlson/parse-crontab if APScheduler doesn't give me something already – Rikaelus Mar 24 '18 at 21:21

1 Answers1

1

The triggers don't work backwards, so you would have to add that functionality to them yourself.

Alex Grönholm
  • 5,563
  • 29
  • 32