SOLVED
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>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
</head>
<body>
<noscript>AEM Cloud Service.</noscript>
<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"
statusApi="https://dev-console-ns-team-aem-cm-prd-n83310.ethos18-prod-va7.dev.adobeaemcloud.com/api/releases/ns...">
</div>
</body>
</html>
1 Accepted Solution
Correct answer by
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.
Aanchal Sikka
Correct answer by
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.
Aanchal Sikka
Related Conversations
