Hi @PovEim , AEM DAM doesn’t provide full usage or search analytics out of the box.Asset Insights only tracks assets used with embed codes or Dynamic Media, not those added via the asset picker - that’s why you see no data.Custom Asset Usage Report:Build a script or report that scans pages/component...

Hi @sams16001423 ,Try this below approch: Use AEM’s activator pattern instead of granite:rel.<workflow-button jcr:primaryType="nt:unstructured" sling:resourceType="cq/gui/components/common/admin/ext/activator" text="Start Workflow" icon="workflow" variant="primary"> <granite:...

Hi @Kamaraj_AEM ,The MCP Server for AEM currently supports reading and analyzing content but does not support direct page creation via AI or API calls out of the box.If you’re using the GitHub version you mentioned, that project mainly exposes content structure for external tools-it doesn’t include ...

Hi @kaniar,This behavior is expected OOTB during deactivation, AEM automatically processes the parent and all its child pages individually, which is why PackageContentBuilder.create() is called multiple times.To implement a custom deactivation flow, you can- Create a custom workflow or service that ...

Hi @MikeHa25 ,AEM doesn’t do it automatically out of the box, but you can easily automate it using Query Builder + scheduled workflow or ACS Commons report to regularly identify and manage outdated content.In AEM, there’s no built-in automation that directly flags or reports outdated pages, but you ...

Hi @test1234567 ,Please check this way if possible:-rep:write is an aggregate privilege that includes jcr:modifyProperties, but if there’s a deny rule higher in the hierarchy (like for the everyone group), it overrides that part of the privilege.So even though your group had rep:write, the deny on j...

Hi @grandhip Please try this below ways:Your problem: AEMaaCS blocks your Java code from making HTTP calls back to itself. It's a security thing in the cloud.Best fix: Don't use HttpClient at all. Instead, use AEM's built-in GraphQL Java client or Content Fragment APIs that work internally without H...

Hi @NageshRaja , For diagnosing missing experience fragments (XFs) in AEM Publish, focus on these logs:audit.log: Tracks user and system actions like deletions and replication requests.replication.log: Shows replication agent status, job successes, or failures.error.log: Provides error details from ...

Hi @grandhip , The “read timed out” error happens because AEM as a Cloud Service blocks or limits direct HTTP calls from backend Java code (like with HttpClient) to its own GraphQL endpoint for security and performance reasons. This works locally, but in the cloud, these calls often get blocked, del...

Hi @NageshRaja , Your experience fragments (XFs) disappeared from AEM Publish and showed 404 errors because of a replication issue or cloud sync problem, even though nobody deleted or deactivated them. This can happen when internal AEM Cloud jobs, replication agent failures, or content package deplo...