-
Notifications
You must be signed in to change notification settings - Fork 972
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
Unable to associate time pattern with minutes. #248
Comments
Hey swateek, I hope I can provide some insight here.
The at definition allows you to schedule the job every Nth day according to the documentation:
|
Assertion says:
I tested it and it works for hours aswell: |
@Yonodactyl when we say every 5 minutes, let's say the process starts at 10:07, the next run would be at 10:12.. right? What I want is irrespective of whatever time it starts (10:07 in this case), the job should run at 10:10, 10:15 and so on.. |
@Bastian82 that piece of code would run the job once every hour. I do have a job that works that way.. with the "at" function. Can you write a similar code to run every 05th minute of hours (like 10:10, 10:15, 10:20, etc.)? |
Yes, this will run code every 33th minute of every hour: As i said it is stated in assertion i mentioned above |
I want a job to run every 5th minute, like 10:00..10:05..10:10
When I tried the below code, it throws up an assertion error.
Currently as a work around, am running it every minute and checking in my code if its the 5th minute of hour. Is there a nicer way to do it via schedule?
The text was updated successfully, but these errors were encountered: