DocumentationExperience Cloud KCS

Metadata editing fails in AEM Assets Essentials due to browser extension interference

Last update: October 22, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article describes an issue where metadata updates in Adobe Experience Manager (AEM) Assets Essentials view fail to save due to interference from browser extensions, and provides steps to resolve the problem.

Description description

Environment

  • Adobe Experience Manager (AEM) Assets Essentials (all versions)

Symptoms

  • When editing or updating metadata for assets in the Assets Essentials view, changes do not save.
  • The issue does not occur in the AEM Assets default view.
  • No error message is shown in the UI, but metadata changes are not persisted.
  • The issue is reproducible in Chrome, but not in Safari or other browsers.
  • Other users and devices are able to update metadata successfully.

Cause

A browser extension in Chrome is interfering with PATCH requests, preventing metadata updates in the Assets Essentials view.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Attempt to update asset metadata in alternative browsers such as Safari or Firefox to confirm if the issue is isolated to Chrome.
  2. In Chrome, open chrome://extensions.
  3. Disable all extensions.
  4. Retry metadata editing in the Assets Essentials view.
  5. Create a new Chrome profile or use a Guest profile with no extensions enabled, then attempt to update metadata again.
  6. Consult with IT to verify if any endpoint security or web-filtering software is blocking PATCH requests to the AEM author endpoint.
  7. If the issue persists, open Chrome DevTools, enable Network logging, and preserve the log. Reproduce the issue and export the HAR file. Redact cookies and authorization tokens before sharing with support.
  8. If metadata editing works after disabling extensions, identify and remove the problematic extension.
  9. If the issue persists, continue using an unaffected browser or the AEM Assets default view as a workaround.
recommendation-more-help
experience-cloud-kcs-help-kbarticles