ExperimentalReadonlyBAD_The handler cannot or will not process the request due to an apparent client error.
Clients should not retry this request unless advised otherwise.
ReadonlyCONFLICTThe request could not be made due to a conflict. This may happen when trying to create an operation that has already been started.
Clients should not retry this request unless advised otherwise.
ReadonlyINTERNALAn internal error occured.
Subsequent requests by the client are permissible.
ReadonlyNOT_The requested resource could not be found but may be available in the future.
ReadonlyNOT_The server either does not recognize the request method, or it lacks the ability to fulfill the request. Clients should not retry this request unless advised otherwise.
ReadonlyREQUEST_Returned by the server when it has given up handling a request. This may occur by enforcing
a client provided Request-Timeout or for any arbitrary reason such as enforcing some
configurable limit.
Subsequent requests by the client are permissible.
ReadonlyRESOURCE_Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
Subsequent requests by the client are permissible.
ReadonlyUNAUTHENTICATEDThe client did not supply valid authentication credentials for this request.
Clients should not retry this request unless advised otherwise.
ReadonlyUNAUTHORIZEDThe caller does not have permission to execute the specified operation.
Clients should not retry this request unless advised otherwise.
ReadonlyUNAVAILABLEThe service is currently unavailable.
Subsequent requests by the client are permissible.
ReadonlyUPSTREAM_Used by gateways to report that a request to an upstream server has timed out.
Subsequent requests by the client are permissible.
An error type associated with a HandlerError, defined according to the Nexus specification.