#[non_exhaustive]
pub enum UpdateConnectorRegistrationErrorKind {
AccessDeniedException(AccessDeniedException),
ConflictException(ConflictException),
ConnectorAuthenticationException(ConnectorAuthenticationException),
ConnectorServerException(ConnectorServerException),
InternalServerException(InternalServerException),
ResourceNotFoundException(ResourceNotFoundException),
ServiceQuotaExceededException(ServiceQuotaExceededException),
ThrottlingException(ThrottlingException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdateConnectorRegistration
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
AppFlow/Requester has invalid or missing permissions.
ConflictException(ConflictException)
There was a conflict when processing the request (for example, a flow with the given name already exists within the account. Check for conflicting resource names and try again.
ConnectorAuthenticationException(ConnectorAuthenticationException)
An error occurred when authenticating with the connector endpoint.
ConnectorServerException(ConnectorServerException)
An error occurred when retrieving data from the connector endpoint.
InternalServerException(InternalServerException)
An internal service error occurred during the processing of your request. Try again later.
ResourceNotFoundException(ResourceNotFoundException)
The resource specified in the request (such as the source or destination connector profile) is not found.
ServiceQuotaExceededException(ServiceQuotaExceededException)
The request would cause a service quota (such as the number of flows) to be exceeded.
ThrottlingException(ThrottlingException)
API calls have exceeded the maximum allowed API request rate per account and per Region.
ValidationException(ValidationException)
The request has invalid or missing parameters.
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.