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
Found error processing record on step02Likely 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
FAILUREstate and On Complete runs.
03How to fix it
- Read the logged error for the step to find what failed for the record.
- For more detail, add
<AsyncLogger name="com.mulesoft.mule.runtime.module.batch" level="DEBUG" />tolog4j2.xml. Avoid it in production with large data sets. - Set
maxFailedRecordson<batch:job>:0stops on the first failed record,-1continues regardless of failures, and any other integer is the threshold. - To process failed records in a later step, use
acceptPolicyandacceptExpressionon that step. - Read the error summary by error type, step and count in the On Complete phase.
04Official documentation
→Related errors
- MULE:UNKNOWNMULE:UNKNOWN means an unknown or unexpected error occurred. It cannot be handled directly by its own type, only by a handler for ANY, so read the error description and cause in the log to find the real failure.
- MULE:EXPRESSIONMULE:EXPRESSION means an error occurred while Mule evaluated a DataWeave expression. Find the expression named in the log, check the values it reads for nulls or wrong types, and add a default or a handler.
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