You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, when I try to use the GraphiQL (Graphical Interface Web of GraphQL) it doesn't work.
When I watch the network tab it says
/graphiql/%3CDGS_GRAPHQL_PATH%3E:1 Failed to load resource: the server responded with a status of 404 ()
Also when I try to perform a query or mutation I get this:
POST https://mysite.com/graphiql/%3CDGS_GRAPHQL_PATH%3E 404
Steps to reproduce
I cannot reproduce 100% of the times, I think it's related with some order of execution or concurrency, because sometimes it happens and sometimes it's not. I'm deploying my application in an Elastic Beanstalk in AWS using CloudFormation for the infrastructure.
In localhost I couldn't reproduce it.
Until I not redeploy the app the problem continue there.
I'm using 5.0.5 version. It always happened with any version. I'm having this problem from time to time from the past year.
Note: A test case would be highly appreciated, but we understand that's not always possible
The text was updated successfully, but these errors were encountered:
Please read our contributor guide before
creating an issue.
Expected behavior
When I use the GraphiQL it should work
Actual behavior
Sometimes, when I try to use the GraphiQL (Graphical Interface Web of GraphQL) it doesn't work.
When I watch the network tab it says
/graphiql/%3CDGS_GRAPHQL_PATH%3E:1 Failed to load resource: the server responded with a status of 404 ()
Also when I try to perform a query or mutation I get this:
POST https://mysite.com/graphiql/%3CDGS_GRAPHQL_PATH%3E 404
Steps to reproduce
I cannot reproduce 100% of the times, I think it's related with some order of execution or concurrency, because sometimes it happens and sometimes it's not. I'm deploying my application in an Elastic Beanstalk in AWS using CloudFormation for the infrastructure.
In localhost I couldn't reproduce it.
Until I not redeploy the app the problem continue there.
I'm using 5.0.5 version. It always happened with any version. I'm having this problem from time to time from the past year.
Note: A test case would be highly appreciated, but we understand that's not always possible
The text was updated successfully, but these errors were encountered: