Exceptions raised in integration, staging and production are sent to Errbit.
You'll want to "watch" each of those instances in order to be emailed when an exception occurs.
Exceptions are automatically cleared on a new deployment.
It's unfortunate but we have a few known/ignorable exceptions that occur every so often. It's generally safe to ignore these but if we start seeing large numbers of them then they should be investigated.
These exceptions will often be seen together when network connectivity issues mean that the static/assets host can't be reached.
-
Slimmer::TemplateNotFoundException
(example) -
NoMethodError: undefined method '<<' for nil:NilClass
(example) -
NoMethodError: undefined method 'replace' for nil:NilClass
(example) -
NoMethodError: undefined method 'attr' for nil:NilClass
(example) -
TypeError: wrong argument type nil (expected Data)
(example)
GdsApi::HTTPServerError
(example)