Two key types of errors can occur when running the streamed batch programs:
These are reported when the batch process completes, together with an estimate of the total number of records which may have been affected. Re-running the batch process should process these chunks correctly, unless some fatal error is occurring during the batch processing. Note that skipped chunks are a relatively rare phenomenon; skipped records are far more likely.
These are also reported when the batch program completes, and entries are added to the log files for the stream(s) which encountered the errors, detailing the error that occurred and the stack trace. There are two possible scenarios for this:
The status of the record will have been changed to remove it from the set of records to be processed and a task will have been created for the business owner. This takes the form of suspending the case and sending a task to the case owner.
The status of the record will not have been changed by this event. The log file(s) should be examined to determine the problem, and the batch process re-run to process these records, once the issue has been resolved.