Saving graphql queries throws 409 error conflict | Community
Skip to main content
A
AneleMzinyati
May 17, 2023

Saving graphql queries throws 409 error conflict

  • May 17, 2023
  • 3 replies
  • 2649 views

Hi There,

please will someone explain why am getting error when saving queries.

<head><title>409 Conflict</title></head>
<body>
<h1>Conflict</h1>
<p>Cannot serve request to /graphql/persist.json/myfolder/test in org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet</p>

<h3>Request Progress:</h3>

 

 

Kindest regards,

Anele

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

    3 replies

    krati_garg
    Adobe Employee
    krati_gargAdobe Employee
    Adobe Employee
    May 17, 2023

    @anelemzinyati Please share the AEM version you are using, if it is Cloud or Non Cloud version.

     

    Request is trying to save GraphQL persisted query on above location: graphql/persist.json/myfolder/test 
    Does this path exist? 
    Also, a screen shot would be appreciated.

      A
      AneleMzinyatiAuthor
      May 17, 2023

       @krati_garg it is Cloud  Version 2022.10.9398.20221020T071514Z


        krati_garg
        Adobe Employee
        krati_gargAdobe Employee
        Adobe Employee
        May 18, 2023

        @anelemzinyati Which endpoint have you chosen. Is it Global Endpoint or Custom Endpoint.
        If you are trying to save persisted query to Custom Endpoint, you might have to add access permissions to your custom endpoint defined at /content/cq:graphql/<<custom endpoint>>

        Also, it can be possible that a persisted query with "my-query" name already exist. You might have to click on + button for creating another persisted query

          A
          AneleMzinyatiAuthor
          May 22, 2023

           This doesnt work

            Manu_Mathew_
            Community Advisor
            Manu_Mathew_Community Advisor
            Community Advisor
            May 17, 2023

            @anelemzinyati it looks like there is a node with the same name, try giving a different name while saving queries. Sometimes it might persist in some past information, try clearing the cache and re-login too. 

              Terms & ConditionsAccessibility statement

              Loading footer...