Skip to content
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

enqueue_at sometimes needs a time duration added to the date to enqueue correctly #667

Open
Freatnor opened this issue Apr 12, 2019 · 0 comments

Comments

@Freatnor
Copy link

Right now we're using a TimeWithZone date saved on an object for the enqueue_at time. In some cases it won't properly enqueue unless I add a duration, for instance:
enqueue_at(object.time_with_zone, HandlerClass, object.id)
vs.
enqueue_at(object.time_with_zone + 1.seconds, HandlerClass, object.id)
In both cases the time passed to enqueue_at() is a TimeWithZone.

The interesting thing is I can see the second job appear in the delayed queue but not the first. However if I use remove_delayed() it will remove both jobs making me think it might be something to do with the timestamp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant