The Data Backbone Endpoint Buffer Manager's gen3 ingest code currently calls RawIngestTask.run() to ingest a single raw file at a time. Upon failure to ingest, it tries to store an error message in a database for ease of monitoring and reporting. Currently due to the batch nature of the gen3 middleware ingest code, the exception raised has a generic message (Some failures encountered during ingestion) and details are output in the debug log. It would be helpful if there could be some kind of fail early/first switch that if set would raise on first error and have a more specific error message in the exception. The debug logging will always be able to have more details. But some way to group errors (or to show same error across ingestion versions) in the DBBBM database records would be useful.