flowable/flowable-engine · warning
Following warnings encountered during process validation
Error message
Following warnings encountered during process validation: {} What it means
After parsing a BPMN model, BpmnParse logs any accumulated validation warnings (e.g. unknown attributes or elements that were tolerated during parse). It is a non-fatal notice logged from execute() when warningBuilder is non-empty; parsing continues and the deployment succeeds.
Solutions
- Read the warning body following this log line to see the specific warnings and fix the offending BPMN elements
- Validate the BPMN XML against the Flowable XSD before deployment
- Regenerate or correct the diagram/elements flagged in the modeler
- If the warnings are benign for your use case, they can be safely ignored since deployment still proceeds
Example fix
// before
<process id="p1"><serviceTask id="t1" flowable:unknownAttr="x"/></process>
// after
<process id="p1"><serviceTask id="t1" flowable:delegateExpression="${bean}"/></process> Defensive patterns
Strategy: validation
Validate before calling
// Validate BPMN before deployment
BpmnXMLConverter converter = new BpmnXMLConverter();
ValidationResults results = converter.validateXml(inputStream, false);
if (!results.getWarnings().isEmpty()) {
results.getWarnings().forEach(w -> logger.warn("BPMN warning: {}", w.toString()));
// fix model or proceed knowingly
} Prevention
- Run the BpmnXMLConverter validation as a build/deploy step
- Keep modeler plugins and Flowable versions aligned
- Review logged warnings after each deployment of changed models
When it happens
Trigger: Deploying or parsing a BPMN XML file whose model contains tolerated validation warnings collected during BpmnParse execution; occurs at the end of BpmnParse.execute() when warningBuilder.length() > 0.
Common situations: Deploying process definitions exported from modeling tools with vendor-specific or slightly non-standard BPMN; upgrading Flowable/Activiti where new validation checks flag previously ignored constructs.
Understand the failure class
Background: Schema validation failed / invalid input schema: payload rejected because its shape doesn't match the expected schema — this error's family across 28 libraries.
Related errors
- Activity needed for multi instance cannot bv found
- ' ' is not valid boolean in mapException with errorCode=…
- end event with cancelEventDefinition only supported inside…
- Error code must not be empty.
- Error Code must not be empty.
AI-assisted analysis of flowable/flowable-engine@d6d39ce1c6 (2026-09-11).
Data as JSON: /api/errors/bb8cbc0082839054.
Report an issue: GitHub.
Appendix: source
Thrown at modules/flowable5-engine/src/main/java/org/activiti/engine/impl/bpmn/parser/BpmnParse.java:197
for (ValidationError error : validationErrors) {
if (error.isWarning()) {
warningBuilder.append(error);
warningBuilder.append("\n");
} else {
errorBuilder.append(error);
errorBuilder.append("\n");
}
}
// Throw exception if there is any error
if (errorBuilder.length() > 0) {
throw new ActivitiException("Errors while parsing:\n" + errorBuilder);
}
// Write out warnings (if any)
if (warningBuilder.length() > 0) {
LOGGER.warn("Following warnings encountered during process validation: {}", warningBuilder);
}
}
}
}
bpmnModel.setSourceSystemId(sourceSystemId);
bpmnModel.setEventSupport(new FlowableEventSupport());
// Validation successful (or no validation)
transformProcessDefinitions();
} catch (Exception e) {
if (e instanceof ActivitiException) {
throw (ActivitiException) e;
} else if (e instanceof XMLException) {
throw (XMLException) e;
} else {View on GitHub (pinned to d6d39ce1c6)