You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a new user. So, please excuse me if I'm not using it as intended.
It accepts every().hour.at("59:59").do(job) but doesn't seem to be doing anything. What am I missing? Also, it seems syntactically inconsistent without the colon preceding the minutes time value.
Wondered if every().hour.at should accept both ":MM:SS" or ":MM". If 2 time values are present, it is interpreted as (minutes, seconds) and if just one time value is present, it is interpreted as minutes.
The text was updated successfully, but these errors were encountered:
Hi! Welcome to Schedule. 😄 You are using schedule exactly as it is intended. 👍
You write that it doesn't seem to do anything, let's investigate! Can you share your some more of your code, including the run_pending part?
The following should schedule the job at the last second before every hour.
schedule.every().hour.at('59:59')
Unfortunately you this is currently a little broken. There is a bug in the latest version (0.6.0) that will cause this code to schedule the job to run at 59:00, instead of 59:59. This bug has been solved in #290 and will be included in the next release.
Firstly, let me thank you for creating this package and making it open source - it's quite elegant actually and it was exactly what I needed for my use case. Second, thanks for responding. I will await the next rel. to pick up the fix. When do you think we can expect the next rel?
Btw, the code you mentioned is exactly what I was using
I'm a new user. So, please excuse me if I'm not using it as intended.
It accepts every().hour.at("59:59").do(job) but doesn't seem to be doing anything. What am I missing? Also, it seems syntactically inconsistent without the colon preceding the minutes time value.
Wondered if every().hour.at should accept both ":MM:SS" or ":MM". If 2 time values are present, it is interpreted as (minutes, seconds) and if just one time value is present, it is interpreted as minutes.
The text was updated successfully, but these errors were encountered: