Skip to content
English
Support request Customer portal Sign in
Go to spire.com
  • There are no suggestions because the search field is empty.

Maritime 2.0 GraphQL returns INTERNAL_SERVER_ERROR

How to workaround INTERNAL_SERVER_ERROR in Maritime 2.0 GraphQL response

This issue is due to underlying cloud provider timeout causing an internal server error. It is a transient error due to network issues. We are working on an architectural change to address this issue. In the meantime we strongly recommend implementing a retry mechanism when calling the Maritime 2.0 API.