DocumentationExperience Cloud KCS

Troubleshooting 503 and unknown errors in AEM as a Cloud Service Developer Console

Last update: October 1, 2026

This article provides steps to troubleshoot and resolve 503 Service Unavailable and unknown error messages encountered when accessing the Developer Console in Adobe Experience Manager (AEM) as a Cloud Service development environments.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service development environment
  • Legacy and new AEM Developer Console interfaces

Issue/Symptoms

  • When you access the legacy Developer Console, it remains on the environment-information loading screen and returns 503 Service Unavailable.
  • In the new Developer Console, you see an unknown error and the OSGi Bundles view doesn’t list bundles.
  • The issue persists even though you have the AEM Administrators product profiles for Author and Publish.

Cause

After you verify the correct Adobe organization and Developer Console access requirements, investigate environment readiness and Developer Console integration configuration. The Developer Console also depends on the appropriate product profiles for the AEM service tier you inspect.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Confirm that you’re in the Adobe organization associated with the affected environment and that your Adobe ID has the required Developer Console access:

    • Have either the Cloud Manager Developer - Cloud Service product profile or the AEM Administrators product profile on AEM Author.
    • Have the AEM Users or AEM Administrators product profile for the Author or Publish service tier you need to inspect.

    Note: New product-profile assignments can take up to 30 minutes to synchronize. After the assignment is applied, sign out and back in, clear browser cookies and local storage if needed, and retry.

  2. Check the affected environment’s status in Cloud Manager:

    • Confirm that the environment is available and isn’t undergoing deployment or maintenance.
    • If a deployment is in progress, wait for it to complete before opening Developer Console.

  3. Open both the legacy and new Developer Console interfaces. Record which interface fails, the displayed error, and whether the OSGi Bundles view loads.

  4. Collect information for troubleshooting:

    • Capture screenshots of the error or unexpected behavior.
    • Use your browser’s developer tools to record a HAR file while reproducing the issue.
    • Record the Developer Console URLs you used.
    • Record the affected environment name and type, and confirm the assigned product profiles.

    Note: HAR files can contain cookies, authorization headers, tokens, and personal data. Sanitize the file before sharing it, and don’t include credentials or session secrets in screenshots or support attachments.

  5. If the issue continues after you verify access and environment readiness, contact Adobe Support and provide:

    • A description of the issue and steps to reproduce it.
    • Screenshots of the error or unexpected behavior.
    • A sanitized HAR file.
    • Confirmation of the assigned product profiles and Adobe organization.
    • The affected environment name and type.

  6. After Adobe Support provides a resolution or configuration update, access the Developer Console again and confirm that environment information loads and the OSGi Bundles view lists bundles.

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