#[non_exhaustive]
pub enum UpdateDatasetEntriesErrorKind {
AccessDeniedException(AccessDeniedException),
InternalServerError(InternalServerError),
InvalidParameterException(InvalidParameterException),
LimitExceededException(LimitExceededException),
ProvisionedThroughputExceededException(ProvisionedThroughputExceededException),
ResourceInUseException(ResourceInUseException),
ResourceNotFoundException(ResourceNotFoundException),
ThrottlingException(ThrottlingException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdateDatasetEntries
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You are not authorized to perform the action.
InternalServerError(InternalServerError)
Amazon Rekognition experienced a service issue. Try your call again.
InvalidParameterException(InvalidParameterException)
Input parameter violated a constraint. Validate your parameter before calling the API operation again.
LimitExceededException(LimitExceededException)
An Amazon Rekognition service limit was exceeded. For example, if you start too many Amazon Rekognition Video jobs concurrently, calls to start operations (StartLabelDetection
, for example) will raise a LimitExceededException
exception (HTTP status code: 400) until the number of concurrently running jobs is below the Amazon Rekognition service limit.
ProvisionedThroughputExceededException(ProvisionedThroughputExceededException)
The number of requests exceeded your throughput limit. If you want to increase this limit, contact Amazon Rekognition.
ResourceInUseException(ResourceInUseException)
The specified resource is already being used.
ResourceNotFoundException(ResourceNotFoundException)
The resource specified in the request cannot be found.
ThrottlingException(ThrottlingException)
Amazon Rekognition is temporarily unable to process the request. Try your call again.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.