AEM as Cloud "Request to Complete Move Operation" workflow getting triggered

[Som_ChaithanyaGo]

Hi Everyone,

We are currently encountering an issue with our AEM as a cloud setup. Our cloud instance is multi-tenant and includes five repositories. We have established Groups specific to our content paths, including an admin user group that has read, write, modify, delete, and replicate access to our content paths.

The issue arises when any user who is part of this admin group attempts to move pages from one hierarchy to another. The move operation completes successfully, but it triggers a workflow called "Request to Complete Move Operation," which then accumulates in the workflow instances. However, when I, as the environment admin, perform the same move operation, the workflow mentioned above does not trigger.

Could you please advise on how to ensure that the workflow does not trigger when users with all permissions (write, read, delete, modify, and replicate) perform the move operation?

Thank you for your assistance in resolving this matter.

[giuseppebaglio]

The "Request to Complete Move Operation" workflow is triggered when users without replication privileges attempt to move pages, serving as an approval mechanism to ensure published content moves are properly synchronized between author and publish instances. The workflow does not trigger for environment admins because they possess replication rights by default.

If the workflow is not in place, moving published pages in AEM's author environment will not automatically update the publish server. This can result in discrepancies where a page exists in both the old and new hierarchies. To prevent content duplication on the live site, it is important that the "request to move operation" workflow remains intact and is not removed.

Please take a look at this page, which explains the details related to this workflow. It also offers a workaround: a step to be added to the workflow to check if a page is published or unpublished. If the page is unpublished, the workflow will end; if it is published, it will proceed to the content approver as usual.