Best Practices Analyzer · pattern code · Repository structure
BPA code INS: Invalid namespaces
When Adobe's Best Practices Analyzer reports INS, it has found invalid namespaces on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Register namespaces through repoinit or rename the nodes.
Can it be fixed automatically?
- Not by Adobe's Content Transformer, which only handles content findings (ACV, CAV, DOPI, OAUI, PCX, REP and URS).
- 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 24 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 INS. 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 INS. Checked 19 October 2026.