-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Job is not scheduled immediately #396
Comments
The docs might not be 100% clear, but its says that it only starts after the defined interval. Quote from the docs: "For example, "@every 1h30m10s" would indicate a schedule that activates after 1 hour, 30 minutes, 10 seconds, and then every interval after that." |
I agree this is confusing and the documentation should be clarified. I don't think I can change it now, though, since that would be backwards incompatible. On the bright side, |
@robfig what about introducing an opt-in flag? This way it would be backwards compatible. |
Job is not scheduled as described as in the doc
For example, the code below will only print once "cron scheduled" instead of twice as expected.
The text was updated successfully, but these errors were encountered: