Feature Request to improve Publication Behavior for Locked Live Copy Pages - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	AEM sites Rollout and publication issue
Use-case:	When a editor rollout and publishes a master page, the publication process start publishing the live copies in random order and fails when it encounters any market page that is locked to a user. This results in inconsistencies leaving the page changes published to few random markets. Ideally this should have completely stopped or skip the locked page, deploy to rest and notify about skipped page.
Current/Experienced Behavior:	The rollout/publication does not follow a predictable sequence and succeed for markets until it encounters locked pages then silently fails making it difficult to track progress There is no summary or report indicating which locales were successfully published and which were skipped. This results in inconsistent rollout and makes it hard to identify which pages need manual intervention Improved
	Before initiating rollout publication, the system should check for any live copy pages that are currently locked by users If any locked pages are detected, halt the entire replication process. Display a clear error message indicating which pages are locked and by whom.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM version - 6.5 AEM service pack - 6.5.22
Customer-name/Organization name:	British Airways(BA)
Screenshot (if applicable):
Code package (if applicable):

[#2]

@sai121 Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-34848. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.