graphql does not denote a Persistent Query Path | Community
Skip to main content
Uppari_Ramesh
Level 5
March 22, 2024
Solved

graphql does not denote a Persistent Query Path

  • March 22, 2024
  • 2 replies
  • 1073 views

Hi Team, getting this response when I execute a AEM servlet which internally calls graphql endpoint and will pass the response to AEM servlet.

 

{
"data": "{\"errors\":[{\"errorType\":\"ServletError\",\"message\":\"Internal Servlet Failure\",\"details\":\"Path: 'test/..../.../.....' does not denote a Persistent Query Path\"}]}",
"status": 500
}

 

any idea on this? 

 

Thanks!!

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 Uppari_Ramesh

Solution:

The issue "does not denote a Persistent Query Path" occurs when you are executing the graphql endpoint and graphql endpoint contains special characters then we will get this internal servlet failure,  does not denote a Persistent Query Path.

 

To fix this, make sure that graphql endpoint doesn't contain special character. In my case ; was causing the issue.

Issue URL: http://localhost:4502/graphql/execute.json/myproject/namesByPath;path=/content/dam/test/......

Working URL:  http://localhost:4502/graphql/execute.json/myproject/namesByPath%3Bpath=/content/dam/test/......

Difference is issue url contains ; and working url contains encoded value of semicolon i.e. %3B. 

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql-api/persisted-queries#encoding-query-url

 

@shashi_mulugu @mayursatav @kautuk_sahni 

2 replies

Shashi_Mulugu
Community Advisor
Community Advisor
March 23, 2024

@uppari_ramesh did u try to execute graphic query directly? Is it working? Can you also post your servlet code, so that we can guide you better???

Uppari_Ramesh
Level 5
March 24, 2024

Hi @shashi_mulugu ,

 

When I execute the graphql endpoint directly, it's working fine. The servlet code that I'm using is working in all environments except one author instance. This is a intermittent issue. Unable to find what could be the issue. 

Uppari_Ramesh
Uppari_RameshAuthorAccepted solution
Level 5
March 26, 2024

Solution:

The issue "does not denote a Persistent Query Path" occurs when you are executing the graphql endpoint and graphql endpoint contains special characters then we will get this internal servlet failure,  does not denote a Persistent Query Path.

 

To fix this, make sure that graphql endpoint doesn't contain special character. In my case ; was causing the issue.

Issue URL: http://localhost:4502/graphql/execute.json/myproject/namesByPath;path=/content/dam/test/......

Working URL:  http://localhost:4502/graphql/execute.json/myproject/namesByPath%3Bpath=/content/dam/test/......

Difference is issue url contains ; and working url contains encoded value of semicolon i.e. %3B. 

 

FYR: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql-api/persisted-queries#encoding-query-url

 

@shashi_mulugu @mayursatav @kautuk_sahni