Hi @Ganthimathi_R ,
Adobe Experience Manager (AEM) sounds like unexpected behavior that may require further investigation. While there may not be a known issue specifically documented for this scenario, there are several potential reasons why irrelevant pages are being activated along with the configured one:
Launch Configuration: Double-check the configuration of your launches to ensure that only the intended pages are included. Ensure that you haven't accidentally included parent pages, sibling pages, or other irrelevant content.
Permissions: Verify that the user initiating the launch has the correct permissions to activate the intended pages and does not have unintended permissions to activate other pages.
Workflow Dependencies: Review any workflows or processes associated with the launch activation. There may be dependencies or conditions triggering activations on additional pages.
Automation or Scripts: Check if there are any automation scripts or custom processes that may be triggering additional activations unintentionally.
Replication Agents: If you're using replication agents to replicate content across environments, ensure that they are configured correctly and are not replicating unintended pages.
Content Structure: Examine the structure of your content hierarchy to identify any relationships or dependencies that may be causing unintended activations.
Logs and Monitoring: Review the AEM logs and monitoring tools to gather more information about the activation process and any potential errors or warnings that may provide clues to the issue.
AEM Support: If you're unable to identify the root cause of the issue, consider reaching out to Adobe Support or consulting the AEM community forums for assistance. They may be able to provide additional insights or assistance in troubleshooting the issue.
By systematically investigating these potential causes, you should be able to identify why irrelevant pages are being activated along with the configured one and take appropriate action to resolve the issue.
