Staging publication fails with a duplicate entry on LayoutSEOEntry error

Issue

• Staging publication is failing in my environment with the following UI error:

An unexpected error occurred with the publish process. Please check your portal and publishing configuration.
The model.resource.com.liferay.layout.seo.model.LayoutSEOEntry [layoutId] could not be imported because of the following error: org.hibernate.exception.ConstraintViolationException: could not execute batch.

• This error is in the logs:

Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '[layoutId]' for key 'IX_63195F59'

Environment

• Quarterly Releases

Resolution

• This issue was fixed in 2024.q3.1 by LPD-35629

Additional Information

• This issue occurs in the rare case when both the master and the homepage share the same layoutId.
• Sharing the same layoutId doesn't immediately cause conflicts since the master's layout is private and the page's layout is public, but attempting to publish changes from staging to production can cause conflicts if there are modifications to both the master and the homepage.
• The conflicts arise during the import of LayoutSEOEntry due to the layoutId ambiguity. This results in an error that prevents publishing from staging.