@contacttomukesh  can you try giving with out any mode.    <?xml version="1.0" encoding="UTF-8"?> <workspaceFilter version="1.0"> <filter root="/apps/my-site"/> // if empty, the mode is "replace" </workspaceFilter>   Ref Link : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-ma...

@mayank-saxena1987  seems what ever you have done is right. But did you update the clientlibs definition ? Modify your client library definitions to point to the new location. This typically involves updating the categories property in the clientlib node. Navigate to http://localhost:4502/libs/cq/ui...

@Heidi05  Did you do any customisation to OOTB feature DM hotspot ?    Refer to below link https://experienceleague.adobe.com/docs/dynamic-media-developer-resources/library/viewers-for-aem-assets-only/interactive-images/customizing-interactive-image/r-html5-aem-int-image-customize-hotspots.html?lang...

@shyamasundar-ks  you can try using -Padobe-public in your maven command

@sivas61374651  Ensure that your bundles are started in the correct order, especially if they have dependencies on each other. Starting bundles in the wrong order can lead to older versions being used. In some cases, dynamic updates of bundles may not work as expected. Make sure that you uninstall a...

@djohn98390536  how did you do the customisation seems you are missing some thing. I tried this in local and it was working fine 

@Vani1012  Ensure that you have the appropriate permissions to access or modify nodes under the /apps/granite/ui/components path. Incorrect permissions could prevent you from seeing or modifying these nodes.

Hi @goyalkritika    Can I know what is the purpose of the API ? are you using any service user to write or create data on jcr ?   If yes, Please check the permissions of that service user

@MeenuRajput     Can you try to validate with the latest version of core components and confirm

@shyamasundar-ks  As you are pretty sure that you did not do any changes to the working code, and it was working earlier and now it's not working.  As suggested by @arunpatidar  can you check the response headers.