This should be the accepted solution. Thanks sandeep

Hi @VivekSr1 It is ideal to use same error page for all content tree and you can configure in dispatcher if you need locale specific error page. If there is any requirement for content tree specific error page then use acs commons error handler https://adobe-consulting-services.github.io/acs-aem-com...

Hi @kautuk_sahni , I suspect there could be some workflow launcher associated with the video mime type which is triggering the workflow. @nithya90 Could you please check the launcher console and and also check error logs on video upload

Hi @zankarshah , I am working on a similar issue, let me know if you found a workaround to fix it

Could you also follow the steps mentioned in this articlehttps://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-17467

Could you check in status of com.day.cq.replication.impl.servlets.ReplicationServlet/system/console/components in the failing publisher 

Did you create the page from crx and could you confirm whether you have jcr:content under this page node

Hi @Anilkumar9 Try to clear cache http://localhost:4502/system/console/scriptcache and click “clear cache” 

hi @Nimma05 Since you have register the resource change listener for language copy any property change in the registered resources will trigger the listener. The methods which helps to identify the property which got updated is deprecated now. 

Create a ResourceChange Listener to the content fragment folder path and clear the dispatcher cache for your servlet path DispatcherFlusher service. Limitation with this approach is dispatcher cache will be removed regardless of any cf get updated under the given path.