Issue Summary

Moving a large amount of pages with Confluence Automation (Move page action) resulted in misleading information in Automation Audit Log.

Steps to Reproduce

1. Create an Automation rule to move a page (using Move page action), similar as below (Automation rule trigger may vary):
   
2. Attempt to move more than 10000 pages in total, by executing the Automation Rule on a parent page with a large amount of descendants (more than 10000 pages).

Expected Results

The Automation Audit Log outlining accurate results of the page move attempts.

Actual Results

The Automation Audit Log outlined that the page moves for some pages are successful, even though they aren't.

The below exception is thrown in the back-end Confluence log, indicating a failed page move:

level: ERROR
   logger: com.atlassian.confluence.pages.DefaultMoveManager
   m: { [+]
   }
   message: Failed to acquire lock #1: [DefaultMoveManager.<SpaceKey>]

However, Automation log and Automation Audit log indicate a successful page move, a few miliseconds after:

message: atlassian-proxy.us-east-1.prod.atl-paas.net:443 PUT /cloudid/<CloudID>/confluence/wiki/rest/api/content/<sourcePageID>/move/append/<targetPageID> HTTP/1.1.
Status: [200].
ATL-TraceId: [<hashValue>].
Took: 12919ms.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available