Avoid cyclic references of the experience fragments OR Show warning message of cyclic references of the experience fragments
Avoid cyclic references of the experience fragments to impact overall instance performance
We had multiple critical situations on Production recently where a misconfiguration by author (causes Cyclic reference) started having huge impact on overall instance performance, taking almost 100% of CPU as well. Publishing the same page resulted in showing service outage exception (Referencetoodeep in the logs) page to the end user.
If author configures cyclic reference of the experience fragment, there will be a warning message OR cyclic reference cannot be configured
Environment Details (AEM version/service pack, any other specifics if applicable):
AEM as a could service & AEM Release: 2023.3.11382.20230315T073850Z
Vergölst GMBH (Continental Reifen Deutschland GmbH)