DocumentationExperience Cloud KCS

AEM as a Cloud Service: Asset Metadata Updated and Asset Deleted Events not triggered from Touch UI

Last update: June 27, 2026

This article explains why certain AEM Assets events, such as Asset Metadata Updated and Asset Deleted, aren’t triggered when actions are performed via Touch UI in AEM as a Cloud Service.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

  • Event registrations for AEM Assets are configured in AppBuilder for a workspace using AEM Cloud Service as the provider.

  • The registration subscribes to the following events:

    • aem.assets.asset.processing_completed
    • aem.assets.asset.metadata_updated
    • aem.assets.asset.deleted

  • When performing asset actions in the AEM Cloud Service DEV author instance:

    • Asset Processing Completed events appear in Debug Tracing as expected.
    • Asset Metadata Updated and Asset Deleted events don’t appear in Debug Tracing when actions are performed on real assets via the Touch UI.
    • When triggering sample events from the Event Registration detail page, all events (including metadata updated and deleted) appear in Debug Tracing.

  • No error messages are shown, but expected events are missing from the trace.

  • Reference: Adobe Experience League Community - Assets Deleted/Asset Metadata Updated Events Not Registering in Adobe I/O

Resolution resolution

  1. Review the event registration configuration in AppBuilder and confirm that the following events are selected:

    • aem.assets.asset.processing_completed
    • aem.assets.asset.metadata_updated
    • aem.assets.asset.deleted

  2. Ensure that the registration uses OAuth S2S for server-to-server credentials and is saved correctly.

  3. When testing event emission:

    • Use the Assets View UI (React-based interface) or the Assets OpenAPI to perform asset metadata updates and deletions.
    • Don’t use the classic Touch UI for these actions, as certain events aren’t emitted from Touch UI.

  4. For asset deletion events:

    • Ensure the asset is permanently deleted from Trash. Moving an asset to Trash doesn’t trigger the aem.assets.asset.deleted event; only permanent deletion does.
    • Understand that asset deleted (repository removal) is distinct from asset removed from delivery (no longer served via delivery URLs).

  5. To verify event emission:

    • Perform the desired action (metadata update or permanent delete) in the Assets View UI or via the OpenAPI.
    • Check Debug Tracing for the corresponding event.

Cause

Certain AEM Assets events, including aem.assets.asset.metadata_updated and aem.assets.asset.deleted, are only emitted when actions are performed via the Assets View UI or Assets OpenAPI, not from the classic Touch UI. Additionally, asset deletion events are only triggered upon permanent deletion from Trash.

recommendation-more-help
experience-cloud-kcs-help-kbarticles