Locating workflow package payload paths in Adobe Experience Manager

This article explains how to locate workflow package payload paths in Adobe Experience Manager (AEM) and provides steps to resolve common access and visibility issues.

Description description

Environment

Adobe Experience Manager (all supported versions)

Issue/Symptoms

  • Unable to find workflow package payload paths in the repository browser.
  • Expected asset sub-paths under a payload path are not visible.
  • Access errors occur when attempting to view the payload from a workflow instance.

Cause

Workflow package nodes are stored under a specific repository path, while the payload path references the content or asset being processed. Missing nodes or access errors can result from insufficient permissions or if the referenced content has been deleted or moved.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Open the repository browser tool for AEM.
  2. Navigate to the /var/workflow/packages path in the repository to locate workflow package nodes related to the workflow instance.
  3. Review the payload path shown in the workflow instance. This path references the content or asset being processed, not the workflow package node itself.
  4. If the payload path doesn’t resolve to an existing node, verify that the referenced asset or content exists and hasn’t been deleted or moved.
  5. If access errors occur when viewing the payload, verify that the user account has sufficient permissions to access both the workflow instance and the payload path, including /var/workflow/packages and the relevant content paths under /content/dam or other applicable locations. For AEM as a Cloud Service, verify that permissions are configured correctly in the Admin Console or through user group assignments.
  6. Review the workflow model configuration to determine whether workflow packages are configured for deletion after workflow completion. Check for any steps or process arguments that control package cleanup.
  7. After making the changes, verify that you can access the workflow package and payload path without errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles