Best Practices Analyzer · pattern code · Repository structure
BPA code CAV: Content in areas that break content classification
When Adobe's Best Practices Analyzer reports CAV, it has found content in areas that break content classification on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Move content out of /libs and other restricted areas; the Content Transformer can relocate it.
Step-by-step fix: Splitting mutable and immutable content packages for AEM Cloud Service.
Can it be fixed automatically?
- Yes, often: the Content Transformer in Cloud Acceleration Manager can fix findings of this type and creates a rollback package first.
- In our pipeline, automation for this pattern is rated high: agents prepare the change and an engineer reviews it.
How much work is it?
Our readiness scan plans about 0.5 hours per finding at MAJOR importance (1.5× for CRITICAL, 0.5× for ADVISORY), plus a small fixed cost, capped at 80 hours for this code. INFO rows are treated as inventory and not costed. These are planning figures, not a quote.
Reading the row in results.csv
Filter the code column for CAV. The importance column says how urgent each row is, identifier usually holds the repository path, and message describes the finding. See how to read a BPA report for every column.
Source: Adobe Pattern Detector documentation for CAV. Checked 19 October 2026.