tag:blogger.com,1999:blog-294680397865315179.post2383357280837170309..comments2010-10-19T09:31:53.906-05:00Ethan Viziteihttp://www.blogger.com/profile/16886242271824345907noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-294680397865315179.post-31778662354381909652010-10-19T09:31:53.906-05:002010-10-19T09:31:53.906-05:00Yes, to the uninformed it would seem like it would be that easy, but you have to realize that this error was not occurring as part of the job, it was happening in the delayed_job library itself as it tried to deserialize the job object to begin processing, and since every DJ process runs through the first few available jobs to find one to run, they all would try to deserialize this job and the whole DJ process would exit. <br /><br />Remember, DJ has built in exception handling for problems that occur during the job run itself. If a job fails during execution it will be setup to rerun later, and the associated DB column will be updated to show what the latest error was.Ethan Viziteihttp://www.blogger.com/profile/16886242271824345907noreply@blogger.comtag:blogger.com,1999:blog-294680397865315179.post-59658526714745262592010-10-19T02:19:22.671-05:002010-10-19T02:19:22.671-05:00umm...how about error handling around a single job. This way even if one of them fails others later in the queue executeAnonymousnoreply@blogger.com