Documentation

Publish Content Tree workflow stuck on running state on AEMaaCS – Assets

Last update: Mon Sep 22 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

The Publish Content Tree workflow in AEMaaCS – Assets gets stuck during asset publishing from the Author environment. To fix the issue, restore the default configurations.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service(AEMaaCS) – Assets
  • Workflow: Publish Content Tree
  • Instance: Development

Issue/Symptoms

  • The Publish Content Tree workflow in Digital Asset Management (DAM) gets stuck in the running state and does not complete when triggered on folders.
  • Logs show the error: ;java.lang.RuntimeException: Unable to deserialize property 'com.adobe.granite.workflow.job'.
  • First two workflow steps complete; later steps fail to execute.
  • Issue persists across payload sizes, including small payloads (For example: 15MB, 81 images).
  • Recursive publishing fails even for minimal content.
  • Quick Publish for individual assets works as expected.

Resolution resolution

To fix the issue, follow these steps:

  1. Verify the Out-of-the-Box (OOTB) configurations for any changes, focusing on alterations to com.adobe.cq.deserfw.impl.DeserializationFirewallImpl.

  2. Ensure custom configurations extend OOTB settings without removing defaults.

  3. If any OOTB entries are missing from your configuration:

    • Restore them by referring to the default configuration.
    • Add your custom changes on top of this restored configuration.

  4. Deploy the updated configuration to your development environment.

  5. Abort all workflows stuck in the running  state.

  6. Start and test a new Publish Content Tree  workflow instance.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f