The operation was aborted, typically due to a concurrency issue like sequencer check failures, transaction aborts, etc.
An attempt to create an entity failed because one already exists.
The requested URL path wasn't routable to a Twirp service and method.
The requested URL path wasn't routable to a Twirp service and method. This is returned by generated server code and should not be returned by application code (use "not_found" or "unimplemented" instead).
The operation was cancelled.
The operation resulted in unrecoverable data loss or corruption.
Operation expired before completion.
Operation expired before completion. For operations that change the state of the system, this error may be returned even if the operation has completed successfully (timeout).
The operation was rejected because the system is not in a state required for the operation's execution.
The operation was rejected because the system is not in a state required for the operation's execution. For example, doing an rmdir operation on a directory that is non-empty, or on a non-directory object, or when having conflicting read-modify-write on the same resource.
When some invariants expected by the underlying system have been broken.
When some invariants expected by the underlying system have been broken. In other words, something bad happened in the library or backend service. Twirp specific issues like wire and serialization problems are also reported as "internal" errors.
The client specified an invalid argument.
The client specified an invalid argument. This indicates arguments that are invalid regardless of the state of the system (i.e. a malformed file name, required argument, number out of range, etc.).
Some requested entity was not found.
The operation was attempted past the valid range.
The operation was attempted past the valid range. For example, seeking or reading past end of a paginated collection. Unlike "invalid_argument", this error indicates a problem that may be fixed if the system state changes (i.e. adding more items to the collection). There is a fair bit of overlap between "failed_precondition" and "out_of_range". We recommend using "out_of_range" (the more specific error) when it applies so that callers who are iterating through a space can easily look for an "out_of_range" error to detect when they are done.
The caller does not have permission to execute the specified operation.
The caller does not have permission to execute the specified operation. It must not be used if the caller cannot be identified (use "unauthenticated" instead).
Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
The request does not have valid authentication credentials for the operation.
The service is currently unavailable.
The service is currently unavailable. This is most likely a transient condition and may be corrected by retrying with a backoff.
The operation is not implemented or not supported/enabled in this service.
An unknown error occurred.
An unknown error occurred. For example, this can be used when handling errors raised by APIs that do not return any error information.