#[non_exhaustive]
pub enum CreateContactFlowModuleErrorKind {
AccessDeniedException(AccessDeniedException),
DuplicateResourceException(DuplicateResourceException),
IdempotencyException(IdempotencyException),
InternalServiceException(InternalServiceException),
InvalidContactFlowModuleException(InvalidContactFlowModuleException),
InvalidParameterException(InvalidParameterException),
InvalidRequestException(InvalidRequestException),
LimitExceededException(LimitExceededException),
ResourceNotFoundException(ResourceNotFoundException),
ThrottlingException(ThrottlingException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateContactFlowModule
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You do not have sufficient permissions to perform this action.
DuplicateResourceException(DuplicateResourceException)
A resource with the specified name already exists.
IdempotencyException(IdempotencyException)
An entity with the same name already exists.
InternalServiceException(InternalServiceException)
Request processing failed because of an error or failure with the service.
InvalidContactFlowModuleException(InvalidContactFlowModuleException)
The problems with the module. Please fix before trying again.
InvalidParameterException(InvalidParameterException)
One or more of the specified parameters are not valid.
InvalidRequestException(InvalidRequestException)
The request is not valid.
LimitExceededException(LimitExceededException)
The allowed limit for the resource has been exceeded.
ResourceNotFoundException(ResourceNotFoundException)
The specified resource was not found.
ThrottlingException(ThrottlingException)
The throttling limit has been exceeded.
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.