Avoid cyclic references of the experience fragments

[#1]

Request for Feature Enhancement (RFE) Summary:	Avoid cyclic references of the experience fragments OR Show warning message of cyclic references of the experience fragments
Use-case:	Avoid cyclic references of the experience fragments to impact overall instance performance
Current/Experienced Behavior:	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.
Improved/Expected Behavior:	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
Customer-name/Organization name:	Vergölst GMBH (Continental Reifen Deutschland GmbH)
Screenshot (if applicable):
Code package (if applicable):

[#2]

@AEMCONTITIRE 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-12888. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#3]

@AEMCONTITIRE This has been accepted.

[#4]

@kautuk_sahni : could you please provide an update about the idea?

Thanks

Xuehang

[#5]

@AEMCONTITIRE, on checking this internally, significant progress has been made. I'll keep you posted once (not so far) there is a public-facing announcement about this.