Graphql failed to load resource: the server responded with a status of 500 (Internal server Error)
|
The 500 code would normally indicate an error on the server, not anything with your code. Some thoughts Show
unread, Oct 24, 2018, 9:57:24 AM10/24/18 to Cerner FHIR Developers We started getting 500s every time we connects to Cerner sandbox to test out app. Tried restarting local app, running on a different machine, clearing browser cache, using other browser, all the usual suspects, with no success. This seems to be an internal server error on Cerner side of things. Application seems to fail when fetching observations. Here are the details: Steps to reproduce: * select localhost application to test * select a test patient * log into sandbox * observe: ** Error 500 in browser console - Failed to load resource: the server responded with a status of 500 (Internal Server Error) The following error is recorded: { "error": { "readyState": 4, "responseText": "Internal service error from resource store", "status": 500, "statusText": "Internal Server Error" }, "data": { "readyState": 4, "responseText": "Internal service error from resource store", "status": 500, "statusText": "Internal Server Error" }, "config": { "query": { "code": { "$or": [
"http://loinc.org|8302-2", "http://loinc.org|3141-9" ] }, "patient": "4342008" },
"type": "Observation", "baseUrl": "https://fhir-ehr.sandboxcerner.com/dstu2/...", "auth": { "bearer": "..." }, "patient": "4342008", "headers": { "Authorization": "Bearer ...", "Accept": "application/json", "Content-Type": "application/json" },
"credentials": "", "method": "GET", "url":
"https://fhir-ehr.sandboxcerner.com/dstu2/.../Observation?code=http%3A%2F%2Floinc.org%7C8302-2%2Chttp%3A%2F%2Floinc.org%7C3141-9&patient=4342008",
"params": {} } } X-Request-Id: 6393be2f15e6b1947b1dd77deef72113 Kind regards, Paul Kevin Maloyunread, Oct 24, 2018, 7:30:47 PM10/24/18 to Cerner FHIR Developers I think this must be a sandbox issue as I am getting 500's when trying Observation k. Orelvis Vazquezunread, Oct 24, 2018, 8:57:17 PM10/24/18 to Cerner FHIR Developers The sandbox is still having internal errors when processing requests to the Observation endpoint. X-Request-Id: 1c907b92a5396afff2f04aa6388ae2aa RESPONSE HEADERS: HTTP/1.1 500 Internal Server Error Date: Wed, 24 Oct 2018 12:46:40 GMT Cache-Control: no-cache Vary: Origin,User-Agent,Accept-Encoding Server-Response-Time: 1556.638107 X-Request-Id: 1c907b92a5396afff2f04aa6388ae2aa Status: 500 Internal Server Error Transfer-Encoding: chunked Content-Type: text/plain; charset=utf-8 RESPONSE BODY: Benjamin Eichhorn (Cerner)unread, Oct 24, 2018, 9:12:44 PM10/24/18 to We are currently experiencing issues with our Observation resource and are currently investigating, we apologize for the inconvenience and will post back with further updates. Thank you, Ben (Cerner) Benjamin Eichhorn (Cerner)unread, Oct 25, 2018, 1:06:09 AM10/25/18 to Thank you for your patience. We have identified the issue and a fix has been made to bring the resource back online. You should now be able to resume calls to the Observation resource. Thank you again for your patience, Ben (Cerner) When Shopify receives a request to an API endpoint, a number of different HTTP status codes can be returned in the response depending on the original request. The request wasn't understood by the server, generally due to bad syntax or because the This status is also returned when the request provides an invalid The requested shop is currently locked. Shops are locked if they repeatedly exceed their API request limit, or if there is an issue with the account, such as a detected compromise or fraud risk. Contact support if your shop is locked. How do I fix failed to load resource the server responded with a status 500?Solution 1
A 500 internal server error just means something went wrong with your code. You'll need to examine your server logs to find out what the problem is and fix it.
How do you handle GraphQL errors?GraphQL default error handling.. Better modelisation of errors using Union and Interfaces.. Implementing Union types based error handling.. Handle those Schema changes into the GraphQL server.. Typesafe error handling on the client-side.. Specific Error classes for all GraphQL schema Error types.. codegen mapping.. What is GraphQL error?GraphQL errors
These are errors related to the server-side execution of a GraphQL operation. They include: Syntax errors (e.g., a query was malformed) Validation errors (e.g., a query included a schema field that doesn't exist) Resolver errors (e.g., an error occurred while attempting to populate a query field)
How do you handle ApolloError?Whenever you throw an ApolloError , you can add arbitrary fields to the error's extensions object to provide additional context to the client. You specify these fields in an object you provide to the error's constructor. id: ID!
|
