DocumentationExperience Cloud KCS

AEM as a Cloud Service: Component deploys locally but not in Cloud due to SDK version mismatch

Last update: October 16, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains why a custom AEM component may deploy successfully on a local SDK but not appear in Cloud Environments, focusing on SDK version mismatches and how to resolve them.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • Local SDK version: 2026.3.*
  • Cloud SDK version: 2026.8.*

Symptoms

  • A custom component (e.g., countdown-clock) is deployed successfully on the local AEM Cloud SDK instance.
  • The component does not appear after deployment to Cloud Environments.
  • No specific error messages are reported, but the component is missing in the cloud environment after pipeline execution.
  • Local deployment works as expected; cloud deployment does not include the component.

Steps to reproduce

  1. Deploy the countdown-clock component to a local AEM Cloud SDK instance (2026.3.*).
  2. Deploy the same codebase to a Cloud Environment using the Cloud SDK (2026.8.*).
  3. Observe that the component is present locally but missing in the Cloud Environment.

Cause

A mismatch between the local and cloud SDK versions can lead to deployment discrepancies, often due to breaking changes or incompatibilities introduced in newer SDK releases.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Ensure that the custom component and its dependencies are compatible with the Cloud SDK version (2026.8.*).
  2. Review the AEM as a Cloud Service SDK Release Notes for breaking changes between 2026.3.and 2026.8..
  3. Confirm that the countdown-clock component is included in the codebase and is not excluded by any build or deployment filters (such as in filter.xml).
  4. Validate that the component is present in the built package (.zip or .jar) before deployment.
  5. Access the Cloud Manager pipeline execution logs for errors or warnings related to the component deployment, and look for skipped or failed package installations.
  6. Set up a local AEM instance using the Cloud SDK version (2026.8.*) and attempt to deploy the component.
  7. If the issue reproduces locally on 2026.8.*, investigate compatibility or dependency issues.
  8. Refactor or update the component to resolve any compatibility issues identified with the newer SDK version.
  9. Rebuild and redeploy the package.

After completing these steps, verify that the component appears in the Cloud Environment.

recommendation-more-help
experience-cloud-kcs-help-kbarticles