Level 2

Error in Product Function Testing step in AEM Cloud

Forum|Forum|9 months ago
May 6, 2025
6 replies
1267 views

While running the build pipeline for the qa environment, I'm experiencing the build error in the Product Functional Testing step. Please find the below logs for the same. Can someone help me out on the same.

2025-05-06 10:19:30,005 [INFO] Scanning for projects...
2025-05-06 10:19:31,197 [INFO]
2025-05-06 10:19:31,197 [INFO] -------------< com.adobe.evergreen.eaas:eaas-test-runner >--------------
2025-05-06 10:19:31,198 [INFO] Building EaaS tests runner 1.0.0
2025-05-06 10:19:31,198 [INFO] from pom.xml
2025-05-06 10:19:31,198 [INFO] --------------------------------[ jar ]---------------------------------
2025-05-06 10:19:31,491 [INFO] Downloading from shared: file:///shared/m2-repo/com/adobe/cq/cloud/com.adobe.cq.cloud.testing.it.smoke/0.21.7/com.adobe.cq.cloud.testing.it.smoke-
<title>Test Page</title>
</head>
<body>
<div class="root responsivegrid">
<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">
<div class="responsivegrid aem-GridColumn aem-GridColumn--default--12">
<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">

<div class="text parbase aem-GridColumn aem-GridColumn--default--12">

<link rel="stylesheet" href="/etc.clientlibs/wcm/foundation/clientlibs/accessibility.lc-6fe5d4427361a4c0ca5a75457e3e4256-lc.min.css" type="text/css">

<p>This page was generated by an automated integration test</p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

at org.apache.sling.testing.clients.util.HttpUtils.throwError(HttpUtils.java:101)
at org.apache.sling.testing.clients.util.HttpUtils.verifyHttpStatus(HttpUtils.java:40)
at org.apache.sling.testing.clients.AbstractSlingClient.doStreamRequest(AbstractSlingClient.java:331)
at org.apache.sling.testing.clients.AbstractSlingClient.doStreamGet(AbstractSlingClient.java:440)
at org.apache.sling.testing.clients.AbstractSlingClient.doGet(AbstractSlingClient.java:503)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.lambda$checkPage$0(ContentPublishRule.java:193)
at org.apache.sling.testing.clients.util.poller.Polling.call(Polling.java:90)
at org.apache.sling.testing.clients.util.poller.Polling.poll(Polling.java:117)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.checkPage(ContentPublishRule.java:198)
... 65 more
2025-05-06 10:30:29,545 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Activating /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5 on publish-internal
2025-05-06 10:30:30,111 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Activation response received ReplicationResponse{code=200, message="Replication started for /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5", artifactId="dstrpck-1746527429887-66f3e07b-1aa6-428d-8579-dd7b38fa3a29"}
2025-05-06 10:30:30,112 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Checking the replication queue [publish-internal] for action [Activate] contains item [pkgId: dstrpck-1746527429887-66f3e07b-1aa6-428d-8579-dd7b38fa3a29] with paths [/content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5]
2025-05-06 10:30:30,172 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Checking page https://publish-p115810-e1152082.adobeaemcloud.net/content/test-site/testpage_13233fe9-5aae-476e-84c... returns status 200
2025-05-06 10:30:30,262 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Page check completed with status 200
2025-05-06 10:30:30,262 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - De-Activating /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5 on publish-internal
2025-05-06 10:30:30,356 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - De-Activation response received ReplicationResponse{code=200, message="Replication started for /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5", artifactId="718b36ae-e048-4623-81b0-863419b83cf5"}
2025-05-06 10:30:30,356 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Checking the replication queue [publish-internal] for action [Deactivate] contains item [pkgId: 718b36ae-e048-4623-81b0-863419b83cf5] with paths [/content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5]
2025-05-06 10:30:30,408 [main] INFO com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - Checking page https://publish-p115810-e1152082.adobeaemcloud.net/content/test-site/testpage_13233fe9-5aae-476e-84c... returns status 404
2025-05-06 10:40:36,469 [main] ERROR com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule - PAGE_AVAILABLE: Failed to check the page /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5.html via the AEM publish ingress (expected status 404). Please ensure that the CDN and Dispatcher configurations allow fetching the page.
com.adobe.cq.cloud.testing.it.smoke.exception.PublishException: PAGE_AVAILABLE: Failed to check the page /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5.html via the AEM publish ingress (expected status 404). Please ensure that the CDN and Dispatcher configurations allow fetching the page.
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.getPublishException(ContentPublishRule.java:210)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.checkPage(ContentPublishRule.java:200)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.checkPage(ContentPublishRule.java:141)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.deactivateAssertPublish(ContentPublishRule.java:244)
at com.adobe.cq.cloud.testing.it.smoke.PublishEndToEndIT.activateAndDeactivate(PublishEndToEndIT.java:103)
at org.apache.sling.testing.clients.util.poller.Polling.call(Polling.java:90)
at org.apache.sling.testing.clients.util.poller.Polling.poll(Polling.java:117)
at com.adobe.cq.cloud.testing.it.smoke.PublishEndToEndIT.testActivateAndDeactivate(PublishEndToEndIT.java:91)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.apache.sling.testing.junit.rules.TestStickyCookieRule$1.evaluate(TestStickyCookieRule.java:34)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement.evaluate(ExistingInstanceStatement.java:62)
at org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement.evaluate(ExistingInstanceStatement.java:62)
at com.adobe.cq.testing.junit.rules.CQUserAgentRule$1.evaluate(CQUserAgentRule.java:33)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
at org.junit.vintage.engine.execution.VintageExecutor.executeClassesAndMethodsSequentially(VintageExecutor.java:93)
at org.junit.vintage.engine.execution.VintageExecutor.executeAllChildren(VintageExecutor.java:73)
at org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:70)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:201)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:170)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:94)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:59)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:142)
at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:58)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:103)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:85)
at org.junit.platform.launcher.core.DelegatingLauncher.execute(DelegatingLauncher.java:47)
at org.junit.platform.launcher.core.InterceptingLauncher.lambda$execute$1(InterceptingLauncher.java:39)
at org.junit.platform.launcher.core.ClasspathAlignmentCheckingLauncherInterceptor.intercept(ClasspathAlignmentCheckingLauncherInterceptor.java:25)
at org.junit.platform.launcher.core.InterceptingLauncher.execute(InterceptingLauncher.java:38)
at org.junit.platform.launcher.core.DelegatingLauncher.execute(DelegatingLauncher.java:47)
at org.apache.maven.surefire.junitplatform.LazyLauncher.execute(LazyLauncher.java:56)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.execute(JUnitPlatformProvider.java:194)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:150)
at org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:122)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
Caused by: org.apache.sling.testing.clients.exceptions.TestingValidationException: Expected HTTP Status: 404 . Instead 200 was returned!
Response Content:

<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>

<script defer="defer" type="text/javascript" src="/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js"></script>
<link rel="stylesheet" href="/etc.clientlibs/foundation/clientlibs/main.lc-b4994788cf1eaeed300a0aa7af53f3c8-lc.min.css" type="text/css">
<script src="/etc.clientlibs/clientlibs/granite/jquery.lc-f9e8e8c279baf6a1a278042afe4f395a-lc.min.js"></script>
<script src="/etc.clientlibs/clientlibs/granite/utils.lc-899004cc02c33efc1f6694b1aee587fd-lc.min.js"></script>
<script src="/etc.clientlibs/clientlibs/granite/jquery/granite.lc-011c0fc0d0cf131bdff879743a353002-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/jquery.lc-dd9b395c741ce2784096e26619e14910-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/shared.lc-e9d9a3990d7779c2e8e3361187f3d36b-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/main.lc-690ba627a9a2eeef0733ede272cf726b-lc.min.js"></script>

<title>Test Page</title>
</head>
<body>

<div class="root responsivegrid">

<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">

<div class="responsivegrid aem-GridColumn aem-GridColumn--default--12">

<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">

<div class="text parbase aem-GridColumn aem-GridColumn--default--12">

<link rel="stylesheet" href="/etc.clientlibs/wcm/foundation/clientlibs/accessibility.lc-6fe5d4427361a4c0ca5a75457e3e4256-lc.min.css" type="text/css">

<p>This page was generated by an automated integration test</p>
</div>

</div>
</div>

</div>
</div>

</body>
</html>
(return code=200)
Request: GET https://publish-p115810-e1152082.adobeaemcloud.net/content/test-site/testpage_13233fe9-5aae-476e-84c...
Response: 200 OK
<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>

<script defer="defer" type="text/javascript" src="/.rum/@adobe/helix-rum-js@%5E2/dist/rum-standalone.js"></script>
<link rel="stylesheet" href="/etc.clientlibs/foundation/clientlibs/main.lc-b4994788cf1eaeed300a0aa7af53f3c8-lc.min.css" type="text/css">
<script src="/etc.clientlibs/clientlibs/granite/jquery.lc-f9e8e8c279baf6a1a278042afe4f395a-lc.min.js"></script>
<script src="/etc.clientlibs/clientlibs/granite/utils.lc-899004cc02c33efc1f6694b1aee587fd-lc.min.js"></script>
<script src="/etc.clientlibs/clientlibs/granite/jquery/granite.lc-011c0fc0d0cf131bdff879743a353002-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/jquery.lc-dd9b395c741ce2784096e26619e14910-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/shared.lc-e9d9a3990d7779c2e8e3361187f3d36b-lc.min.js"></script>
<script src="/etc.clientlibs/foundation/clientlibs/main.lc-690ba627a9a2eeef0733ede272cf726b-lc.min.js"></script>
<title>Test Page</title>
</head>
<body>

<div class="root responsivegrid">

<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">
<div class="responsivegrid aem-GridColumn aem-GridColumn--default--12">

<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">

<div class="text parbase aem-GridColumn aem-GridColumn--default--12">

<link rel="stylesheet" href="/etc.clientlibs/wcm/foundation/clientlibs/accessibility.lc-6fe5d4427361a4c0ca5a75457e3e4256-lc.min.css" type="text/css">
<p>This page was generated by an automated integration test</p>
</div>

</div>
</div>
</div>
</div>

</body>
</html>

at org.apache.sling.testing.clients.util.HttpUtils.throwError(HttpUtils.java:101)
at org.apache.sling.testing.clients.util.HttpUtils.verifyHttpStatus(HttpUtils.java:40)
at org.apache.sling.testing.clients.AbstractSlingClient.doStreamRequest(AbstractSlingClient.java:331)
at org.apache.sling.testing.clients.AbstractSlingClient.doStreamGet(AbstractSlingClient.java:440)
at org.apache.sling.testing.clients.AbstractSlingClient.doGet(AbstractSlingClient.java:503)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.lambda$checkPage$0(ContentPublishRule.java:193)
at org.apache.sling.testing.clients.util.poller.Polling.call(Polling.java:90)
at org.apache.sling.testing.clients.util.poller.Polling.poll(Polling.java:117)
at com.adobe.cq.cloud.testing.it.smoke.rules.ContentPublishRule.checkPage(ContentPublishRule.java:198)
... 67 more
2025-05-06 10:40:37,643 [main] INFO com.adobe.cq.testing.junit.rules.Page - Deleted page at /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5
2025-05-06 10:40:37,658 [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1230 s <<< FAILURE! -- in com.adobe.cq.cloud.testing.it.smoke.PublishEndToEndIT
2025-05-06 10:40:37,658 [ERROR] com.adobe.cq.cloud.testing.it.smoke.PublishEndToEndIT.testActivateAndDeactivate -- Time elapsed: 1230 s <<< ERROR!
java.util.concurrent.TimeoutException: Call failed to return true in 60000 ms. Last exception was: com.adobe.cq.cloud.testing.it.smoke.exception.PublishException: PAGE_AVAILABLE: Failed to check the page /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5.html via the AEM publish ingress (expected status 404). Please ensure that the CDN and Dispatcher configurations allow fetching the page.
at org.apache.sling.testing.clients.util.poller.Polling.poll(Polling.java:133)
at com.adobe.cq.cloud.testing.it.smoke.PublishEndToEndIT.testActivateAndDeactivate(PublishEndToEndIT.java:91)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at org.apache.sling.testing.junit.rules.TestStickyCookieRule$1.evaluate(TestStickyCookieRule.java:34)
at org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement.evaluate(ExistingInstanceStatement.java:62)
at org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement.evaluate(ExistingInstanceStatement.java:62)
at com.adobe.cq.testing.junit.rules.CQUserAgentRule$1.evaluate(CQUserAgentRule.java:33)

2025-05-06 10:40:39,091 [INFO] Running com.adobe.cq.cloud.testing.it.smoke.GetTogglesIT
2025-05-06 10:40:39,293 [main] INFO com.adobe.cq.testing.junit.rules.ConfigurableInstance - Using instances with config: [authentication method: LoginToken, indexing lanes detection: false]
2025-05-06 10:40:39,294 [main] INFO com.adobe.cq.testing.junit.rules.ConfigurableInstance - Using instances with config: [authentication method: LoginToken, indexing lanes detection: false]
2025-05-06 10:40:39,296 [main] INFO org.apache.sling.testing.junit.rules.instance.util.ConfigurationPool - Reading initial configurations from the system properties
2025-05-06 10:40:39,296 [main] INFO org.apache.sling.testing.junit.rules.instance.util.ConfigurationPool - Found 2 instance configuration(s) from the system properties
2025-05-06 10:40:39,299 [main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - InstanceConfiguration (URL: https://author-p115810-e1152082.adobeaemcloud.net, runmode: author) found for test com.adobe.cq.cloud.testing.it.smoke.GetTogglesIT
2025-05-06 10:40:39,299 [main] INFO org.apache.sling.testing.junit.rules.instance.ExistingInstanceStatement - InstanceConfiguration (URL: https://publish-p115810-e1152082.adobeaemcloud.net, runmode: publish) found for test com.adobe.cq.cloud.testing.it.smoke.GetTogglesIT
2025-05-06 10:40:41,790 [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.617 s -- in com.adobe.cq.cloud.testing.it.smoke.GetTogglesIT
2025-05-06 10:40:41,808 [INFO]
2025-05-06 10:40:41,808 [INFO] Results:
2025-05-06 10:40:41,808 [INFO]
2025-05-06 10:40:41,808 [ERROR] Errors:
2025-05-06 10:40:41,808 [ERROR] PublishEndToEndIT.testActivateAndDeactivate:91 » Timeout Call failed to return true in 60000 ms. Last exception was: com.adobe.cq.cloud.testing.it.smoke.exception.PublishException: PAGE_AVAILABLE: Failed to check the page /content/test-site/testpage_13233fe9-5aae-476e-84cf-cbbd7a42e7b5.html via the AEM publish ingress (expected status 404). Please ensure that the CDN and Dispatcher configurations allow fetching the page.
2025-05-06 10:40:41,809 [INFO]
2025-05-06 10:40:41,809 [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
2025-05-06 10:40:41,809 [INFO]
2025-05-06 10:40:41,813 [INFO] ------------------------------------------------------------------------
2025-05-06 10:40:41,813 [INFO] BUILD SUCCESS
2025-05-06 10:40:41,813 [INFO] ------------------------------------------------------------------------
2025-05-06 10:40:41,815 [INFO] Total time: 21:11 min
2025-05-06 10:40:41,815 [INFO] Finished at: 2025-05-06T10:40:41Z
2025-05-06 10:40:41,815 [INFO] ------------------------------------------------------------------------

narendiran_ravi

Level 6

Hi @shyamsundar ,

The error appears to be related to a delay in the deactivation process. Please verify if the replication queue is blocked. Additionally, I recommend re-running the pipeline, as delays in deactivation can occasionally lead to this issue.

ShyamSundarAuthor

Level 2

Hi @narendiran_ravi
I have run the build couple of times, the pipeline seems to be stuck in the same step (at Product Functional Testing)
Please suggest some other way.
Thanks !

AmitVishwakarma

Community Advisor

Hi @shyamsundar ,

Based on the logs you've provided, the Product Functional Testing step is failing because of a mismatch in expected HTTP status code during a publish-deactivation test in AEM Cloud.

The test expected an HTTP 404 (Not Found) after deactivating a page from the publish environment, but it actually received a 200 OK, meaning the page was still accessible.

Expected HTTP Status: 404 . Instead 200 was returned!
...
<p>This page was generated by an automated integration test</p>

This indicates that the page was not fully deactivated or still being served by the CDN/Dispatcher layer even after the deactivation request was acknowledged successfully.

Likely Causes and Fixes

1. CDN/Dispatcher Caching Delay
- Cause: The page may still be cached by the Dispatcher or CDN (e.g., Fastly).
- Fix: Ensure the CDN/Dispatcher is properly invalidating content on deactivation. Check that statfileslevel and invalidate rules are set correctly in your Dispatcher config.

2. Flush Agent Misconfiguration
Cause: The flush agent for your publish environment might not be configured properly or is slow to propagate.
Fix: Check the replication agent logs in AEM (/etc/replication/agents.publish) and ensure it's flushing as expected.

3. Health Check Delay in Test
Cause: The test may be checking the page status too soon after deactivation before the cache is actually purged.
Fix: Consider adding a delay/retry logic in the test or adjusting the polling timeout.

4. Unexpected Dispatcher Configuration
Cause: The Dispatcher might be set to serve stale content even after activation/deactivation cycles.
Fix: Review your dispatcher.any config files, especially under:
- /cache
- /statfileslevel
- /invalidate
- /rules

5. Publish Environment Delay or Sync Issue
Cause: The replication logs show it started, but the test might run before it completes or before the publish instance syncs.
Fix: Verify the publish instance is up-to-date and the replication queue is clear.

Next Steps
- Confirm the test page is actually deactivated in publish (check directly on the publish instance, bypassing CDN if needed).
- Temporarily disable CDN caching or bypass it to isolate the issue (e.g., add a cache-busting header or query param).
- Check your dispatcher flush logs and test with statfileslevel = 2 or higher if needed.
- If it’s reproducible, try rerunning the test with an artificial delay between deactivate and the 404 check

Regards,
Amit

muskaanchandwani

Adobe Employee

@shyamsundar Please validate the Publisher Access, Dispatcher, CDN Logs of the Environment corresponding to the time frame the Pipeline was executed, for the problematic URL :

/content/test-site/testpage_53977d8b-cbd8-45c7-bad8-362f6e31b09c.html

This will help isolate the cause of the Problem - i.e., if the issue is at the Replication/Distribution (AEM Publish), Dispatcher, or CDN Level

ShyamSundarAuthor

Level 2

@muskaanchandwani @amitvishwakarma - What will be consequence of skipping the product functional testing step in the build ?
Is it possible to skip the product functional testing step in stage or prod?
Kindly let me know.

rks1108

Adobe Employee

Please ensure that the CDN and Dispatcher configurations allow fetching the page.

As per the above error:

Do you have the ServerAlias localhost in your vhost?
Add those suggested ServerAlias in the vhost and try again.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/caching#cache-activation-deactivation

aanchal-sikka

Community Advisor

@shyamsundar Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Aanchal Sikka

kautuk_sahni

Community Manager

@shyamsundar Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded