Enum aws_sdk_honeycode::Error
source · #[non_exhaustive]
pub enum Error {
AccessDeniedException(AccessDeniedException),
AutomationExecutionException(AutomationExecutionException),
AutomationExecutionTimeoutException(AutomationExecutionTimeoutException),
InternalServerException(InternalServerException),
RequestTimeoutException(RequestTimeoutException),
ResourceNotFoundException(ResourceNotFoundException),
ServiceQuotaExceededException(ServiceQuotaExceededException),
ServiceUnavailableException(ServiceUnavailableException),
ThrottlingException(ThrottlingException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
All possible error types for this service.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You do not have sufficient access to perform this action. Check that the workbook is owned by you and your IAM policy allows access to the resource in the request.
AutomationExecutionException(AutomationExecutionException)
The automation execution did not end successfully.
AutomationExecutionTimeoutException(AutomationExecutionTimeoutException)
The automation execution timed out.
InternalServerException(InternalServerException)
There were unexpected errors from the server.
RequestTimeoutException(RequestTimeoutException)
The request timed out.
ResourceNotFoundException(ResourceNotFoundException)
A Workbook, Table, App, Screen or Screen Automation was not found with the given ID.
ServiceQuotaExceededException(ServiceQuotaExceededException)
The request caused service quota to be breached.
Remote service is unreachable.
ThrottlingException(ThrottlingException)
Tps(transactions per second) rate reached.
ValidationException(ValidationException)
Request is invalid. The message in the response contains details on why the request is invalid.
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.