New jobs not recognized on Elastic Beanstalk

[rmatovu987]

I have a rails 8 app that is using solid queue.

Everything runs perfectly on development, also when deployed with Kamal.

The issue comes when we deploy with AWS Elastic Beanstalk. Solid queue on AWS EB only recognizes jobs that were there at the initial deployment. All jobs created afterwards give an error when triggered with perform_later, however they run well when triggered with perfrom_now.

The error is:
SolidQueue-1.1.3 Error in thread (0.0ms) error: "NameError uninitialized constant Exports"

In addition, the jobs that were there at the initial deployment are not reconfigured if you push a new update for example, I had a job which run every 1 hour to perform some task, and I modified the contents of the task and changed it to run once per day, and I re-deployed. The job kept running the original way and still runs every 1 hour.

We have two environments, one is a web server environment and the other is a worker environment.

What could be the issue?

[rosa]

It sounds like your Solid Queue deployment is not being properly restarted when you deploy new code there?