Request for Feature Enhancement (RFE) Summary: New content fragment editor console doesn't show the "Source Edit" option despite being enabled and visible. It appears correctly on the old/classic console Use-case:Our Content Fragment Model has a multi-line text field configured with default type as ...

Hi Everyone,   Is it just me or recently in our AEM Cloud Manager - Developer console - The consoles to view the configurations or services are sluggish. This is true for the classic console especially. Most of the times the classic consoles are timing out or saying "Failed to fetch"   While the ne...

Hey @JyothiM, For dispatcher error handling do you have DispatcherPassError enabled along with ErrorDocument?If you are unable to handle this at dispatcher you can probably use a Sling Filter to intercept requests, check if the user has access and then redirect to custom error page.Here's a sample c...

Most likely the time zones for the servers are not in sync maybe, the time stored in JCR is usually UTC based so that it doesn't depend on local time zone. Can you check the timestamp stored in JCR? Are your AEM Cloud server and AMS server based out of same zone or are different? Ideally this should...

Hey @NageshRaja,   The launches are stored at path /content/launches. You can use create packages as snapshots and migrate them to the AEM Cloud instance. As its already content freeze for migration window you don't have to worry about migrating new launches and do it in one pass. Hope this helps!  ...

Yes, I hope the product profile for users or admin have also been assigned to the respective users for AEM instance access.

Hi @sailesha,I am not sure if there is an exact time documented but typically it takes 15-20 mins to see the changes reflected on the AEM instances. https://www.aemtutorial.info/2024/11/how-to-synchronize-adobe-ims-user.html To quote from the above blog - User & Group Sync delays between AEM and Ad...

Hi @NageshRaja,   I noticed you had earlier asked query about RDE deployment failed status. If you were able to deploy previously but not now then something has changed with respect to the Cloud Manager. As @aanchal-sikka mentioned, reach out to your IT Team to understand any org level access change...

Congratulations @arunpatidar 

@kolluax - Can you also check whether the vhost section to ensure the request is routed correctly?Also can you ensure the cache is disabled as well? /rules { /0001 { /glob "*" /type "allow" } } The logs point to the CSRF token endpoint not being handled. Can you also add the below? /filter { /0001 {...