-
Notifications
You must be signed in to change notification settings - Fork 70
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
Support dispatching recurring task immediatly #97
Comments
Hey @Intrepidd, that's definitely on my mind! I want to support it as well, but I want to change how tasks are stored right now. The current implementation relies on the dispatcher's metadata and doesn't do any kind of serialization to the arguments. The job class is not a problem, but the arguments might be. This is also related to rails/solid_queue#186 and rails/solid_queue#183. I think I'd rather get that one straightened out, possibly storing the tasks separately and properly serializing the arguments, and then tackle this one that would be trivial. |
This would be super awesome, was just checking the recurring tab in the hope there would be a "Run" button there. Great minds think alike 💡 |
This will be coming very soon after I finally got rails/solid_queue#272 |
This is done in #199 and will be available in version 0.5.0. Solid Queue >= 1.0.1 required. |
It would be great to be able to dispatch a new job for a recurring task straight from the mission control recurring task page.
I would love to make a PR for it, any pointers ? My naive approach would be to add a new controller and simply call
perform_later
on the job class.The text was updated successfully, but these errors were encountered: