We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am trying to find a gem that will allow me to combine prioritization in Sidekiq with scheduling.
Sidekiq currently has a perform_at method that allows me to set a certain time for a job, but if two jobs are scheduled for the same time, which wins?
I am trying to do something like:
AnnouncementScheduler.perform_with_priority_at(:low, " 2016-07-08 08:34:53 -0400", a.id) AnnouncementScheduler.perform_with_priority_at(:very_high, " 2016-07-08 08:34:53 -0400", b.id)
where the scheduling conflict would resolve in favor of the second one, due to priority.
I just wondered if your gem already does this, as I don't see anything for that in the documentation, but often miss things.
The text was updated successfully, but these errors were encountered:
@nilatti i am facing the same challenge. Can you share the solution for this problem
Sorry, something went wrong.
No branches or pull requests
I am trying to find a gem that will allow me to combine prioritization in Sidekiq with scheduling.
Sidekiq currently has a perform_at method that allows me to set a certain time for a job, but if two jobs are scheduled for the same time, which wins?
I am trying to do something like:
AnnouncementScheduler.perform_with_priority_at(:low, " 2016-07-08 08:34:53 -0400", a.id)
AnnouncementScheduler.perform_with_priority_at(:very_high, " 2016-07-08 08:34:53 -0400", b.id)
where the scheduling conflict would resolve in favor of the second one, due to priority.
I just wondered if your gem already does this, as I don't see anything for that in the documentation, but often miss things.
The text was updated successfully, but these errors were encountered: