-
Notifications
You must be signed in to change notification settings - Fork 125
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
GetOccurrences -- Issue #39
Comments
Unfortunately this problem relates to the format itself, please see this section on Wikipedia:
|
It will be nice to introduce a 'warning' for such cases. A daily (an external) user is not aware abot this specific limitation and thus expect coorect results. For example: if the user have passed a not accurate frequencies (according to values from that article), do log info-message with suggestion of this limitation (maybe add this link to Wiki article). |
I think adding it to the docs is sufficient, and as far as I can see it has been explained in the docs as
|
When cron expression is set to run job at every 30+ mints, for example "*/40 * * * *", it shows next occurrences as
8/6/2021 3:40:00 AM
8/6/2021 4:00:00 AM
8/6/2021 4:40:00 AM
8/6/2021 5:00:00 AM
8/6/2021 5:40:00 AM
8/6/2021 6:00:00 AM
8/6/2021 6:40:00 AM
8/6/2021 7:00:00 AM
8/6/2021 7:40:00 AM
8/6/2021 8:00:00 AM
It's not continuing the 40 mints gap between the executions.
The text was updated successfully, but these errors were encountered: