DocumentationExperience Cloud KCS

AEM solution for Groovy Console access and execution failures

Last update: July 21, 2026

In Adobe Experience Manager as a Cloud Service, the Groovy Console can fail to open or deny script execution because runtime code-execution tools that depend on immutable repository paths are not supported. Confirm that the issue matches this pattern, then move the task to a supported approach such as code deployed through Cloud Manager.

Description description

Environment

Adobe Experience Manager as a Cloud Service

Issue/Symptoms

You may be unable to open the Groovy Console or run a script in Adobe Experience Manager as a Cloud Service.

  • You see a permission error such as You do not have permission to run scripts in the Groovy Console.
  • The Groovy Console UI does not load at paths such as /groovyconsole or /apps/groovyconsole.html.
  • Changing permissions for the console path does not resolve the problem.
  • You can confirm that this article applies by checking that the environment is AEM as a Cloud Service and the environment URL includes adobeaemcloud.com.
  • You can also confirm the issue when the same behavior continues even after reviewing user or group access, because the limitation is platform-based rather than permission-based.

Resolution resolution

Try the following steps to solve the issue:

  1. Confirm that the affected environment is Adobe Experience Manager as a Cloud Service. If the environment URL includes adobeaemcloud.com, that confirms this solution applies. If the environment is not AEM as a Cloud Service, use guidance for that deployment type instead.
  2. Verify the exact symptom by opening the Groovy Console and attempting to run the required task. If the console does not load or shows a permission error instead of running the script, the behavior matches this issue.
  3. Do not try to restore access by changing permissions on /apps or by updating Groovy Console settings. If those changes do not make the console available, that confirms the limitation is related to platform support rather than user permissions.
  4. Replace the Groovy Console task with a supported implementation. Use code deployed through Cloud Manager for packaged changes, or use another supported approach for content updates that does not depend on runtime script execution in the hosted environment. If the replacement approach avoids runtime changes to immutable repository areas, it meets the platform requirements.
  5. Validate the replacement approach in a development environment before promoting changes. If the required update or maintenance task completes successfully and the target content or configuration reflects the change, the replacement has been verified.

If the following symptoms occur and the troubleshooting steps produce the following results, submit a ticket to Adobe Support:

  • The environment is Adobe Experience Manager as a Cloud Service, but the behavior does not match the symptoms described in this article.
  • You need help replacing a legacy Groovy Console process with a supported implementation.
  • A supported feature or deployment path fails while you are moving away from the Groovy Console.

Contact Adobe Support.

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