11.16Batch failures don't necessarily stop everything

This is one of the best features.

Suppose:

100,000 records

and customer #432 is bad.

You usually don't want:

record #432 fails
↓
entire 100k job stops

Mule Batch tracks record success/failure and can continue processing other records based on step policies.

That's ideal for:

data migration
large synchronization
ETL