Getting 503 First Byte timeout with querybuilder on Aem as cloud service?

Hi

For the above query I am not getting response from querybuilder.

I am getting below error

<!DOCTYPE html>

<head>

</head>

<body>

<div id="root" status="503" backend="91530c0b88d94723658fbdea70611f93--F_Skyline_Origin_Ingress_Author" healthy="1"

gen="0" rid="c353be71-c5cf-45a9-9840-6819d71ee958" xid="1768318060" age="0.000" ttl="0.000" restarts="0"

nobranding="true"

</div>

</body>

</html>

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by aanchal-sikka

Hello @akshaybhujbale

The query that you have shared in screenshot would traverse a lot of pages. It might be failing at backend after reaching Max traversal limit.

Please find-tune your query to be more exact. Like a smaller sub-tree.

When in doubt about queries, always check logs for Traversal errors.

https://wttech.blog/blog/2020/jcr-query-performance/ explains about Explain Query tool, which helps you identify if an Index is picked for a query or not.

Level 4

Check if you have enough permissions and query execution rights.

Also verify if query debugger is enabled.

Also verify this in your local SDK if it is working as well.

Finally try to reduce the size of query and add limit to 1 instead of -1

Hope this is helpful.

Accepted solution

Community Advisor

The query that you have shared in screenshot would traverse a lot of pages. It might be failing at backend after reaching Max traversal limit.

Please find-tune your query to be more exact. Like a smaller sub-tree.

When in doubt about queries, always check logs for Traversal errors.

https://wttech.blog/blog/2020/jcr-query-performance/ explains about Explain Query tool, which helps you identify if an Index is picked for a query or not.

Aanchal Sikka