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
Using cached code #1151
Comments
Is |
@nomasprime what makes you think it is using old code? It sounds like maybe you're not restarting the workers after a deploy. See the Restarting docs: https://github.com/collectiveidea/delayed_job#restarting-delayed_job |
I've restarted many times and still the same result, spent the whole day trying to debug. Only I have development and test environments deployed on Azure. With similar input they were both acting unexpectedly and different to local development. I tried everything I could think of and I'm starting to wonder if relating to Docker build process. Restarted container where I ran the clear cache command and still works though. |
Just ran |
@nomasprime i am experiencing the same issue |
Unfortunately when running with Rails in production Delayed Job insists on using old, presumably cached, code.
Surprisingly, after searching the issue to death, there doesn't seem to be any clear info on how to deploy this gem in production.
The text was updated successfully, but these errors were encountered: