Getting SearchpathLimit Error in Logs on trying to hit few pages

[Veena1]

Hi All,

I wanted to understand why am i getting this below error in logs on hitting few pages.

10:17:23.120 *ERROR* [148.252.141.237 [1737109042752] GET /content/path/EN/Sample/products/product-category.html HTTP/1.1] com.day.cq.wcm.core.impl.designer.SearchPathLimiter No style has been found until search path threshold: 10000 was reached.

I am thinking because of the huge content and nested structure authored on page something like below

Each of these paragraph systems have lot of static components and nested structure. Increasing the threshold to 10000 under Design Factory Config will resolve the issue but i dont think its a proper fix and wanted to understand the reasons leading to exceeding default threshold.

[Peter_Puzanovs]

Hey Veena,

Does enabling day cq core debug filter and acs aem commons filter give you any hints as to how you can optimize your page better?

Regards,

Peter

[Veena1]

Hi @Peter_Puzanovs i see day cq wcm debug filter its not enabled. im not certain with the steps on enabling acs commons for hints to optimize page. could you be more specific on ACS commons ways.

[AmitVishwakarma]

Hi @Veena1 ,

AEM tries to resolve styles (like CSS classes, design configs) for components by traversing the component hierarchy upwards from the request path, looking for a matching designPath. When:

  - The page has deeply nested parsys and containers.

  - Each component adds layers to the structure.

  - There are no styles defined (or accessible) at higher levels.

  - AEM reaches the threshold (default: 1000 or 10000) while traversing.

It throws the error.

Try below solution:

Step 1: Fix the Page Structure

You should not increase the threshold unless you're forced to. Instead:

  - Flatten your component hierarchy – reduce deeply nested containers/parsys.

  - Audit your page using CRXDE Lite or curl to count depth levels.

  - Consolidate similar components under one wrapper where possible.

Step 2: Ensure cq:designPath is Properly Set

Make sure your page (or a parent page template) has:

cq:designPath = /etc/designs/<your-site>

If this is missing or wrongly set, AEM cannot resolve design styles, and will traverse needlessly.

Step 3: Audit the Design Configuration

Verify:

  - The referenced designPath exists.

  - The structure under /etc/designs/<your-site> or /conf/<your-site> has valid style definitions for the components being used.

 Regards,
Amit

[Veena1]

@AmitVishwakarma Thanks for the details.

Is it possible to reach 10000 threshold even with static components in picture?

i think having threshold of 10000 is still more.

is it also because every node that is traversed its details will also be saved with AEM scripts running in the background?

[Veena1]

And the design path is    cq:designPath = apps/settings/wcm... set under EN folder of below path

/content/path/EN/Sample/products/product-category.html

[kautuk_sahni]

@Veena1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

[Veena1]

Hey @kautuk_sahni not exactly but yes good path to answer was suggested by advisors.

Thank You