-
Notifications
You must be signed in to change notification settings - Fork 961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next run information is incorrect #58
Comments
@Toshibass are you sure that job was just run? If this message is printed right before the first run, it is perfectly valid. |
Ok so here's another example ,,, 2015-10-17 09:57:04 - schedule - INFO - Running job Every 3 minutes do ESP_keep_alive() (last run: 2015-10-17 09:54:03 next run: 2015-10-17 09:57:03) this time is 1 second in the past, surely the info should say the next time this schedule will run is 2015-10-17 10:00:03 then at that time..... you will see... 2015-10-17 10:00:04 - schedule - INFO - Running job Every 3 minutes do ESP_keep_alive() (last run: 2015-10-17 09:57:03, next run: 2015-10-17 10:03:04) I guess the only time the original INFO makes sense is if you change "next run" to "this run" but that's not very useful information especially if the job is scheduled in days, surely this makes more sense, INFO its now xx running job, last time job ran was yesterday at xx, next time job will run is tomorrow at xx Toshi |
This has confused some people in the past. Let's include that discussion in #30. Thanks for your question. Closing this so we can keep the tracker clean of loose ends. Feel free to follow up (or make a separate issue) with more questions/discussion 😃 |
I have mentioned this previously, I run schedule each day with result:
2015-10-02 18:00:00 - schedule - INFO - Running job Every 1 day at 18:00:00 do delete_kwh() (last run: [never], next run: 2015-10-02 18:00:00)
The problem is the next run information it says 2015-10-02 but it just ran that job so it should say the next run is tomorrow like next run: 2015-10-03 18:00:00)
The text was updated successfully, but these errors were encountered: