Cloud Manager code scan failures and override behavior issues
Adobe Experience Manager as a Cloud Service (AEMaaCS) Cloud Manager code scans fail when Critical or Important code quality metrics do not meet deployment requirements. This issue occurs because Cloud Manager enforces code quality gates that block deployments for Critical issues and conditionally allow overrides for Important issues based on pipeline configuration. The issue affects deployment progress, pipeline execution, and code promotion to target environments. To resolve the issue, fix violations, validate overrides, and rerun pipelines.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- The pipeline fails with
FAIL_CRITICAL_METRICSduring the Code Quality step. - The pipeline pauses on Important issues and displays an Overridden warning when a previous override exists.
- The Cloud Manager UI shows zero Critical issues while the CSV report contains Critical or Major findings.
- The Override option is unavailable in the pipeline UI.
Root cause
The issue occurs because Cloud Manager enforces a three-tier code quality model consisting of Critical, Important, and Info metrics. Critical issues always block deployment and do not support overrides. Important issues pause deployment and support overrides only when the pipeline type and configuration allow them. Differences between the UI and CSV results occur because the CSV contains raw scan findings while the UI displays metric-derived results. Override options are unavailable when failures are Critical or when the pipeline type does not support overrides.
Resolution resolution
Follow these steps to identify the failure category and resolve the code scan issue successfully.
- Identify whether the pipeline failure contains Critical or Important issues by reviewing the Code Quality step in the failed pipeline execution.
- Validate discrepancies between the Cloud Manager UI and the CSV report by downloading the CSV results and reviewing rule IDs, severities, and file references.
- Resolve Critical issues by correcting the code violations identified in the CSV report because Critical issues do not support overrides.
- Determine whether the pipeline supports overrides by reviewing the Important issues section and verifying that the current pipeline type allows override functionality.
- Confirm that the assigned role includes Deployment Manager, Project Manager, or Business Owner permissions when override approval is required.
- Suppress valid false positives by applying the appropriate
@SuppressWarningsannotation for the affected rule and rerunning the pipeline. - Validate the Important metric behavior setting by reviewing the configured pipeline behavior and verifying that it matches business requirements.
- Verify that the build step completes successfully before troubleshooting override behavior because build failures prevent code quality override availability.
- Validate the resolution by confirming that the pipeline passes the Code Quality step or proceeds through an approved override path, that Critical issues return to zero, and that the CSV and UI results align with expected values.
When to escalate
- Critical issues persist after all identified code fixes are applied.
- The override option remains unavailable after validating the pipeline type and assigned role.
- The CSV report contains rule IDs or severity classifications that do not match expected behavior.
- The UI and CSV results continue to show inconsistent severity information after validation.