Resolve folder visibility issues on publish instances in AEM as a Cloud Service - Assets
Folders aren’t appearing on publish instances in AEM as a Cloud Service - Assets, due to configuration discrepancies between authoring and publishing environments. To resolve this issue, check for closed user groups (CUGs), replicate the issue in different environments, remove problematic nodes, verify the resolution, and monitor for recurrence.
Description
Environment
Adobe Experience Manager as a Cloud Service - Assets (AEMaaCS - Assets) (Production)
Issue
Folders that are visible and accessible on the authoring instance aren’t accessible on the publish instance. You can’t access assets from specific directories within the Digital Asset Management (DAM) system. The issue might occur without any recent folder move operations and could happen even when replication logs don’t show any DELETE actions for the affected folder.
Resolution
To resolve this issue where a folder is missing from the publish instance:
- Check if a Closed User Group (CUG) is associated with the problematic folder. For instance, applying the Employee-Asset-superuser CUG to
/content/dam/test-dam, resulted in visibility issues on publish instances. - Attempt to replicate the issue in a local, development, or staging environment by applying similar configurations. Confirm whether removing or modifying CUG settings resolves visibility problems.
- Coordinate with internal customer development and technical teams to delete or adjust nodes related to CUGs under the affected folders across all publish instances.
- After making changes, verify that assets are now visible and accessible on all intended publish instances.
Keep track of reoccurrences of similar issues and ensure proper logging is set up for future troubleshooting.
Related reading
Closed User Groups in AEM in the AEM 6.5 User Guide.