Product functional test failure in Cloud Manager pipeline

Product functional tests can fail during Cloud Manager pipeline deployments when required permissions are missing or when a hidden.cqactions.html node affects access control.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites
  • Cloud Manager

Issue/Symptoms

  • Pipeline fails at the product functional test step during deployment.

  • Error indicates that CreatePageAsAuthorUserIT cannot create a page under /content/test-site.

  • The log message shows:

    code language-none
    2026-02-24 05:21:27,532 [ main]  ERROR com.adobe.cq.testing.client.CQClient - Page creation timed out. Last Exception:     org.apache.sling.testing.clients.ClientException: Sending WCM Command 'createPage' failed!
    
    code language-none
    at com.adobe.cq.testing.util.WCMCommands.executeWCMCommand(WCMCommands.java:676)        at com.adobe.cq.testing.util.WCMCommands.createPage(WCMCommands.java:92)        at com.adobe.cq.testing.client.CQClient$1CreatePagePolling.call(CQClient.java:142)        at org.apache.sling.testing.clients.util.poller.Polling.poll(Polling.java:117)        at com.adobe.cq.testing.client.CQClient.createPageWithRetry(CQClient.java:149)        at com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT.createTestPage(CreatePageAsAuthorUserIT.java:129)        at com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT.testCreatePageAsAuthor(CreatePageAsAuthorUserIT.java:87)    ...    Caused by: org.apache.sling.testing.clients.exceptions.TestingValidationException: Expected HTTP Status: 200 401 . Instead 400 was returned!    Error Message:     Cannot create page (Parent page path should exist)(return code=400)    Request: POST https://author-pYYYYY-eZZZZZ.adobeaemcloud.net/bin/wcmcommand    Response: 400 Bad Request<html>    ...
    
    code language-none
    2026-02-24 05:21:32,341 [ ERROR]  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.53 s <<< FAILURE! -- in com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT    2026-02-24 05:21:32,342 [ ERROR]  com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT.testCreatePageAsAuthor -- Time elapsed: 72.20 s <<< ERROR!    org.apache.sling.testing.clients.ClientException: Failed to create page testpage_eb79313a-6ee3-4e51-ba26-363a7c100679 in 60584
    
    code language-none
    at com.adobe.cq.testing.client.CQClient.createPageWithRetry(CQClient.java:154)        at com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT.createTestPage(CreatePageAsAuthorUserIT.java:129)        at com.adobe.cq.cloud.testing.it.smoke.CreatePageAsAuthorUserIT.testCreatePageAsAuthor(CreatePageAsAuthorUserIT.java:87)    ...    Caused by: java.util.concurrent.TimeoutException: Call failed to return true in 60000 ms. Last exception was: org.apache.sling.testing.clients.ClientException: Sending WCM Command 'createPage' failed!
    

    2026-02-24 05:22:02,164 [ ERROR]   CreatePageAsAuthorUserIT.testCreatePageAsAuthor:87->createTestPage:129 » Client Failed to create page testpage_eb79313a-6ee3-4e51-ba26-363a7c100679 in 60584

  • The .cqactions.html node exists under /content/test-site, impacting required permissions.

Resolution resolution

  1. Verify that the /content/test-site path exists in the AEM repository.

  2. Review access control lists on /content and /content/test-site:

    1. Ensure that authoring groups have jcr:read and jcr:write permissions.
    2. Remove any deny jcr:all permissions for the everyone group.
  3. Check whether a hidden .cqactions.html node exists under /content/test-site:

    1. If it does, prepare a content package or migration script to remove it.
    2. Deploy the package or script through the Cloud Manager pipeline to Stage and Prod environments.
  4. After applying these changes, re-run the Cloud Manager pipeline to confirm that product functional tests complete successfully.

Notes:

  • Avoid making ad-hoc permission changes directly on /content/test-site that could recreate the .cqactions.html node with restrictive access controls.
  • Product functional tests are mandatory for Stage and Prod deployments. They are disabled only in Dev environments.
  • The .cqactions.html node stores AEM UI action and permission data. When this node has restrictive ACLs, it blocks internal test users from completing required actions during automated tests.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f