Hi @Marcos_aem check this out - Solved: Regarding Moving page in AEM 6.5 - Adobe Experience League Community - 549809

Hi @Mario248  To troubleshoot the issue of custom metadata not appearing in AEM Cloud, you need to check permissions, replication, and indexing. First, ensure that the user has the necessary permissions to view and access the custom metadata schema properties, and that they have been added to the ap...

Hi @at_mahajan23 You can setup below paths in sling logs in debug mode  com.day.cq.wcm.core.impl.VersionManagerImplcom.day.cq.wcm.core.impl.VersionPurgeTaskcom.adobe.granite.maintenance.impl.* Additionally refer below links, you may get some more info on the issuehttps://experienceleaguecommunities....

@sue1976 statfileslevel set to 0 invalidates all the content. see below doc references on dispatcher configuration Configuring Dispatcher | Adobe Experience ManagerDispatcher cache invalidation not working - After ... - Adobe Experience League Community - 197954Solved: what is the best approach to a...

@SkyGazer try to update filter.xml available at ui.content/src/main/content/META-INF/vault/filter.xml path with mode='merge' and  see it it works. ie:  <filter root="/content/dam/banner" mode="merge"/>

@ashwinissrinivas what do you mean by partially blocking and not completely blocking, can you share your ask in details, what file types you want to block/allow and relevant configurations you made?

@mayanks21529814  Did you get a chance to disable/enable the ExpiryNotificationJobImpl component?Install AEM vanilla instance in your local and see if you can reproduce the issue and share the steps please to reproduce the issue.  and if you are able to reproduce the issue in aem vanilla instance yo...

@SkyGazer  at first place it seems that you are importing parent /content/dam folder from remote server and due to that all the assets are getting imported again in your local, which might be updating modified date of imported assets. work around to solve this problem is selective commit, instead of...

 @mayanks21529814  setup the debug level logs at below path[0] and see what value you are getting for limit variable, it looks "asset expiry limit" variable value is not setting up as expected in your instance.  [0]cq.dam.expiry.notification.schedulercom.day.cq.dam.core.impl.ExpiryNotificationJobImp...

Hey @mayanks21529814 can you make the changes in Asset expiry Notification job as below It seems that "Asset expiry limit" value is not configured correctly which is causing the issue.