Is this what you want?

def do_something
  # some code here
  begin
    # something that could go wrong here
  rescue Exception => e
    YourMailer.delay.your_method(e.to_s)
    # don't know what you want to delete, but you can do it here
  end
end

ruby on rails - Handle Errors with Delayed Job, Isn't there the possibility to handle errors with delayed_job gem? I would like to find a way (runtime) to send an email to a given account while the errors occur� Queuing Jobs Don’t Delete Failed Jobs. By default, delayed workers delete failed jobs as soon as they reach the maximum number of Think about the Maximum Run Time Value. You may want to consider what value the maximum run time configuration attribute Don’t Use One Queue. Don’t use the default

Found the solution here : http://blog.salsify.com/engineering/delayed-jobs-callbacks-and-hooks-in-rails

# config/initizalizers/delayed_job.rb

class ExceptionMailerPlugin < Delayed::Plugin

  callbacks do |lifecycle|
    lifecycle.around(:invoke_job) do |job, *args, &block|
      begin
        # Forward the call to the next callback in the callback chain
        block.call(job, *args)
      rescue Exception => error
        ErrorMailer.exception_mail(error)
        # Make sure we propagate the failure!
        raise error
      end
    end
  end

end


Delayed::Worker.plugins << ExceptionMailerPlugin

Exception handling with DelayedJob � Issue #35 � wildbit/postmark , I've been reviewing issue #19 to clear up the best way to handle postmark exceptions. I thought I'd found the answer I was looking for but it� Millions of Americans have dealt with crashing websites and never-ending wait times to file for unemployment. Experts say these are the most common mistakes that can delay an application — here

Not that code above doesn't report all the problems .. We recently got a lot issues on worker dynos and we were not even aware about them because we were listening for errors only ...

DelayedJob knows 2 type of errors - errors and failures. In our case - failures were triggered on lower level because we were using Octopus gem. Failure message was: undefined method[]' for nil:NilClass`

class DelayedJobExceptionPlugin < Delayed::Plugin
  def self.report_error(exception, job, type: 'error')
    Airbrake.notify(
      exception, 
      error_message: "#{exception.class.name}: #{exception.message}",
      backtrace: exception.backtrace,
      component: 'DelayedJob Worker',
      type: type,
      parameters: {
        failed_job: job.inspect
      },
    )
  end

  callbacks do |lifecycle|
    lifecycle.around(:invoke_job) do |job, *args, &block|
      begin
        # Forward the call to the next callback in the callback chain
        block.call(job, *args)
      rescue Exception => exception
        DelayedJobExceptionPlugin.report_error(exception, job)

        raise error
      end
    end

    lifecycle.after(:failure) do |job| # Note - some jobs did not trigger Airbrake.notify if we do not use failure!
      exception = ::RuntimeError.new('DelayedJob Failure')
      DelayedJobExceptionPlugin.report_error(exception, job, type: 'failure')

      raise exception if Rails.env.test?
    end
  end
end

Delayed::Worker.plugins << DelayedJobExceptionPlugin

DelayedJob Error Handling Exception � Issue #489 � bugsnag , Description The bugsnag gem causes errors when handling DelayedJob errors. This overrides the DelayedJob last_error field, and also what� What is delayed_job?. Delayed_job lets you run background tasks with your Rails application. It uses your database as a queue to process background jobs. If your app has a high database load, using delayed_job may not be a good background queuing library for your project and you should have a look at Sidekiq or Resque.

Delayed Jobs Callbacks and Hooks in Rails, If your app makes heavy use of Delayed Jobs, this is a useful pattern for be used for adding lifecycle callbacks to handle requirements like these. For example, here's a plugin that we use to report all job errors to Airbrake:� Dismiss Join GitHub today. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.

Delayed Job Best Practices, One gem that can help you handle this need is delayed_job. There are Some exceptions received by Delayed Job can be quite lengthy. Like many Ruby shops we use the DelayedJob job runner to run many of our background tasks. The New Relic agent has had some basic DelayedJob instrumentation for a while now but until recently you were limited to a few metrics which could only be viewed using the somewhat limited and unwieldy custom charts.

I don't see any log messages from delayed job in my rails logs or delayed job log file, the only messages I see are jobs starting/success/failure in the delayed_jobs.log file. this is causing big problems, including detecting bugs and memory leaks in workers almost impossible! Please help!