You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: the method BatchItemProcessingJob#rescue_from will execute if there's an exception raised at some point during the deserialization process. Errors can occur for a variety of reasons, one of which is a faulty connection to the database.
In such case, the BatchItem will not be retrievable (and will end up being nil), which causes batch_item.update to raise a subsequent error, and we never get to see the message inside of exception.message.
Done when: we call Rails.logger.warn exception.message inside of BatchItemProcessingJob#rescue_frombefore the call to batch_item.update.
Or... we need to at least log exception.message in a place where we'll find it if we go looking. I would think the most obvious place would be the Rails log.. but open to suggestions.
The text was updated successfully, but these errors were encountered:
Background: the method
BatchItemProcessingJob#rescue_from
will execute if there's an exception raised at some point during the deserialization process. Errors can occur for a variety of reasons, one of which is a faulty connection to the database.In such case, the
BatchItem
will not be retrievable (and will end up beingnil
), which causesbatch_item.update
to raise a subsequent error, and we never get to see the message inside ofexception.message
.Done when: we call
Rails.logger.warn exception.message
inside ofBatchItemProcessingJob#rescue_from
before the call tobatch_item.update
.Or... we need to at least log
exception.message
in a place where we'll find it if we go looking. I would think the most obvious place would be the Rails log.. but open to suggestions.The text was updated successfully, but these errors were encountered: