“Request for Deletion” workflow is not working in AEM Sites
In AEM Sites, when you delete content pages without the replicate permission, the system triggers the Request for Deletion workflow.
To fix this, ensure you have the correct permissions before initiating deletions and limit the number of simultaneous deletions to reduce workflow load on the system.
Description description
Environment
- Product: Adobe Experience Manager (AEM) Managed Services - Sites, v6.5
- Instance: Production
Issue/Symptoms
- Content pages were deleted by a user with Read, Create, Modify, and Delete permissions.
- After deletion, the pages no longer appeared in the repository (e.g., site console or CRXDE), but they remained accessible.
- When attempting to delete pages without “replicate” permission, AEM triggered the “Request for Deletion” workflow.
- Over 100 workflows were triggered as a result.
Observed behavior
- The workflows consistently entered an ABORTED state when manually completed.
- Attempts to use the ACS Commons Bulk Workflow tool also resulted in aborted workflows.
- The issue persisted even when using accounts with Administrator or workflow-admin privileges.
- Occasionally, workflows completed successfully when executed by users within the Administrator group.
Resolution resolution
Note:The issue has been identified as requiring further analysis by Adobe’s engineering team and is pending a product update for resolution.
Current Workarounds
- Ensure that users initiating page deletions have appropriate permissions, including replicate, to avoid triggering unnecessary workflows.
- If possible, limit the number of simultaneous deletions to reduce workflow load on the system.
Next Steps
- Monitor release notes for updates related to this issue from Adobe’s engineering team.
- If immediate assistance is required or additional information becomes available about your environment, consider reaching out to Adobe support referencing this issue.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f