Open edwinthinks opened 2 years ago
When executing jobs, the worker should rescue these errors here, but it's possible for deserialization failures to crash workers if a lifecycle hook (typically from a plugin) that runs outside of that run
method attempts to deserialize a job (e.g. by calling payload_object
). Is there a more complete stacktrace that might point to a particular plugin you are using?
Hello there,
We noticed that our workers when encountered with a delayed job that specifies a deleted object in its handler cause the workers to crash and halt processing more jobs.
It appears that this raise error is intentional but is I think it is odd that the worker would flat out crash and not just move on if there was an issue. Is there a way to make these errors occur but not crash our workers (we are using heroku dynos)
Any help would be great!