When running API Governance validation in Anypoint Design Center (the in-browser experience), validation fails. One or both of the following errors may appear.
Error 1 - shown in the UI when clicking the "Validate with governance" / "Validate ruleset" button:
{
"info": {
"platform": "Chrome 1xx.x.x.x on Windows 10 64-bit"
},
"error": {
"message": "Custom validator exited unexpectedly",
"name": "CustomValidatorError"
}
}
Error 2 - may appear in the browser console (often alongside Error 1), especially on large projects:
{
"error": {
"message": "Root file model not found"
}
}
Additional observations:
- The failures are intermittent and are more likely on complex APIs with many fragments and custom rulesets.
- Governance auto-validation may not trigger automatically for complex projects (for example, when publishing a version to Exchange in Development state); the manual Validate button is then used and produces the errors above.
- Most reproducible on large projects where the governance content is still loading when the Validate button becomes clickable.
API Governance validation in Design Center can surface two distinct errors, each with its own root cause and workaround.
1) "Custom validator exited unexpectedly" / CustomValidatorError
- Root cause: The custom validator has stability issues when executed in the in-browser JavaScript runtime used by Design Center, so it intermittently fails.
- Workaround: Run API Governance validation in a JVM environment instead of the Design Center browser -> Use Anypoint Code Builder (ACB) with Governance, where this failure does not occur.
2) "Root file model not found"
- Root cause: On large projects, the governance has not finished rendering at the moment the "Validate with governance" button becomes clickable. Clicking it before rendering completes produces this error.
- Workaround: Wait a few seconds before clicking "Validate with governance".
Reference:
- Known Issue: https://help.salesforce.com/s/issue?id=a028c00000zDoA1AAK
005387220

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.