Yes, even we tried the same using replication API. but it is not working. Cache in the dispatcher is not getting cleared or as mentioned in the thread above, that file will be deleted when we execute the code. It is not happeningsnippet looks something like this. ReplicationOptions options = new Rep...

Since it is a AEMaaCS, we can't do that as well.is there any other option for this?

@aanchal-sikka Yes, that is an option but it is not aligned with the use case.we have to clear the cache with selector in the URL. URLs can be as follows./content/abc/xyz/test.sample1.html/content/abc/xyz/test.sample2.html/content/abc/xyz/test.sample3.html Now, all of these page cache need to be cle...

We have tried this.Since the resource,/content/abc/xyz/test.sample.html doesn't exist, we get the warning com.adobe.cq.cloudconfig.core.impl.ConfigurationReplicationEventHandler Resource [/content/abc/xyz/test.sample.html] not found for ReplicationAction. Page cache has not been cleared and we are s...

We have a scenario where we have some dynamic page. These pages have been handled by AEM dispatcher( and getting cached in AEM dispatcher. These pages do not exist in AEM instance.As a next step, we have to clear the cache for these pages using replication API. The page URL contains a selector in th...

@pradeepdubey82  Can you please check and share logs while performing this activity?

@AEMLearner-1989 A similar use case has been discussed in the thread below.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/multi-tenant-deployments-using-cloud-manager/td-p/364123 The correct marked answer in the above thread might be interesting for you.I hope it helps!

Hi @Anudeep_Kumar  Could you please share the use-case?How are you planning to use the node name after defining it?

@SDusane Are you still facing the issue?and could you please share, how are you deploying the code to AEM (via pipeline would be preferred)

Yes, all renditions have been generated correctly.