-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Should be able to specify seconds in RecurringJobScheduler #167
Comments
This would be great 👍 |
NCrontab 2.0 released! Now we need to prepare Hangfire's |
Good that it has been released. And I agree, it would be terrible to query every second. I do need to schedule some jobs to run every 20 seconds, or every 45 seconds. |
Just curious - what kind of background processing do you want to perform every 20 seconds? |
Emailed you separately about that ㊙️ |
In my case in will be summarizing data from a ElasticCache and sending it to a Splunk System |
Hi, I am currently testing 1.40, but I cannot see that it was updated. Hangfire works great, but I have one job that needs to run everything 30 seconds..Is there a workaround to this? |
Hi @bahram-hodjaev i tested this and this does not work, any update on this? i have a job that needs to run every 30 seconds. Thanks in advance :) |
Is there an update on this? |
how about enqueue delayed jobs in every minute? if 5 second granularity needed there will be 30 jobs every minute |
This is also something we'd be interested in as the hacks we have in place at the moment are a little hampering |
This would be a very useful feature! |
This feature would be awesome!! 👍 |
I believe this is coming with Cronos |
Does anyone know when we can expect this release? |
This is a log awaited feature, we'd use it immediately! |
Очень жду! |
Support for seconds implemented in the latest betas of 1.7.0 so you can just pass six-part cron expression and it will work. However, you'll need to tweak the |
The
RecurringJobScheduler
should be able to set a job to reoccur every X seconds.There is support for this in NCrontab see #7, although a build has not yet been released.
I think it would involve making a change here, such that
CrontabSchedule.Parse
takes a second options argument, where you specify that you want to recognise six-part crontab expressions.The text was updated successfully, but these errors were encountered: