AI is a great tool to enhance our experience and reduce our effort. Relying entirely on AI/GEN AI in its current form is not ideal. It is always useful to validate and fact-check the responses.   Empathizing with the user's context might help. Always check before posting. Is this information useful ...

@Chaithanyaj In the log screenshot, I see there is 401 error. This means it is authentication issue. So, I would check admin api_key is configured correctly and has proper access. Here is a user guide for publishing content for EDS which might be helpful.https://experienceleague.adobe.com/en/docs/ex...

@VanitaNa Can you check if there is an overlay for "/libs/granite/ui/content/shell/header/actions" under "/apps"  Here you will see a property like "text_commentI18n" or "text" for each of the action nodes. 

@rkody Got it.Is this happening across all components or just the asset share commons page?Can you check the template policies, if they are updated? Is there any inheritance on this component which locks it so you won't be able to edit it.

@rkody Is this consistent? This happens sometimes when with me on other pages as well. I clear the cache or close the browser and refresh it, the wrench icon shows up. Did you try that already?

@kchaura Got it. For that I see an example for selector deny in this guide, can you check that. This might be similar to what Anil has provided using "/selectors" filter https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration#example-filter...

@kchaura Can you check the order in which deny and allow are added? Did you add deny first and allow later? Also there is an earlier question related to this which Arun answered.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/disable-jcr-content-json-from-url-on-publisher-i...

@SamikshaSh1 In AEMaaCS, when you hit publish instance it will go through CDN and dispatcher. Did you try caching these headers like arunpatidar suggested above? That should solve your problem.

@Shubham_borole Haven't seen this issue.Commenting to follow to see the response form Adobe.

@Samikshash If you are directly hitting the publish url, CDN doesn't come into picture. In this case, are you hitting the publish instance directly ? You should follow what @arunpatidar explained about caching these header to see them.