Manage Unhandled Exceptions
Learn how to manage the unhandled exceptions in our Rails application.
We'll cover the following...
Exception handling
When an exception happens that is not rescued explicitly by our code, it bubbles up a large call stack inside Rails for some sort of handling. If the code was initiated by a controller, Rails will render a default HTTP 500 error. If the code was started by a Rake task, nothing special will happen. If run from a background job, it might be retried, or it might not, it depends. In any case, we need to be able to view and examine these unhandled exceptions because they indicate a problem with our app.
Certainly, unhandled exceptions aren’t business outcomes, but they are a useful bit of telemetry to explain what’s happening with our app. Often, unhandled exceptions indicate bugs in the app that need to be fixed to avoid creating ...