MuleSoft · Batch

Found error processing record on step

Short answer

"Found error processing record on step" is logged when a record fails inside a batch step. By default the job then stops and the instance ends in a FAILURE state, so fix the record error or set maxFailedRecords to control how many failures are tolerated.

VerifiedLast verified

01Error text

MuleSoft error
Found error processing record on step

02Likely causes

  • A record raised an error in a batch step. Only the first record that fails on a step is logged; later identical failures on that step are not, for performance.
  • With the default strategy, the job stops, the instance is set to a FAILURE state and On Complete runs.

03How to fix it

  1. Read the logged error for the step to find what failed for the record.
  2. For more detail, add <AsyncLogger name="com.mulesoft.mule.runtime.module.batch" level="DEBUG" /> to log4j2.xml. Avoid it in production with large data sets.
  3. Set maxFailedRecords on <batch:job>: 0 stops on the first failed record, -1 continues regardless of failures, and any other integer is the threshold.
  4. To process failed records in a later step, use acceptPolicy and acceptExpression on that step.
  5. Read the error summary by error type, step and count in the On Complete phase.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.