Repository navigation
unable to retry on SolidQueue::ProcessExitError #313
Description
hello again!
After updating to V0.6 we naturally started getting failed jobs with SolidQueue::ProcessExitError as the error causing the job to fail.
This looked like a perfect candidate of an exception that we should always retry so i tried adding the following to ApplicationJob:
retry_on SolidQueue::ProcessExitError, wait: :polynomially_longer, attempts: 5unfortunately it seems that this error class is not known to the application:
app/jobs/application_job.rb:16:in `<class:ApplicationJob>': uninitialized constant SolidQueue::ProcessExitError (NameError)
SolidQueue::ProcessExitError,
^^^^^^^^^^^^^^^^^^
Did you mean? SolidQueue::Processes
from app/jobs/application_job.rb:1:in `<top (required)>'
any ideas as to why this class is not loaded in the rails app?
maybe because the supervisor is loaded in another process (docker container in my case) and not the server process where jobs are actually scheduled?
Activity
rosa commentedon Aug 30, 2024
Ohhh, yes! Agh, my fault. The
SolidQueue::ProcessExitErrorclass is not set up properly in a way that Zeitwerk can load it. It's loaded for Solid Queue because the file is loaded anyway before forking, but that won't be the case where you enqueue the job.I'll fix it and will release a new version with the fix shortly.
Move error classes to their own files so they can be loaded by Zeitwerk
Move error classes to their own files so they can be loaded by Zeitwerk
rosa commentedon Aug 30, 2024
Released v0.6.1 with the fix. The error is now
SolidQueue::Processes::ProcessExitError.Move error classes to their own files so they can be loaded by Zeitwerk