-
Notifications
You must be signed in to change notification settings - Fork 103
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
Dynamic scheduled tasks #186
Comments
@wollistik, no, this is not supported yet, you didn't miss it 😅 This is something we can consider adding for sure. May I ask what's your use case for it? |
Hi @rosa,
Therefore the dynamic scheduling feature was really nice to implement these requirements. But after I thought about this the last two days, I might be completely redesign this feature and come up with a different solution, because it was rarely used and still required some quirks to get it working. |
Ahh got it! That makes sense 👍 Yes, I thought a bit more about it yesterday and this is something I want to implement eventually 😊 |
Maybe this helps, but the way I implemented dynamic cron schedules is by having one job run every minute and check if the cron schedule matches the one stored in my database table, with my table containing cron expressions. I use Fugit to check if the cron matches the current time. |
@abrunner94 Even I have done a similar thing. Mine is not exactly the cron like scheduling but I am having different schedules. |
Hi @rosa,
I really appreciate the work you have done here and I am eager to switch over to solid_queue. There is only one thing left, which is holding me back.
Other gems like resque-scheduler or sidekiq-scheduler offer the ability to dynamically add or remove tasks to the schedule (see https://github.com/resque/resque-scheduler?tab=readme-ov-file#dynamic-schedules). Since everything seems to be stored in the database for solid_queue, this should be quite easy to achieve.
Maybe it is only a documentation issue and it is already possible (this would be awesome 🤞 ).
Happy to hear from you!
The text was updated successfully, but these errors were encountered: