#[non_exhaustive]
pub enum CreateSlackChannelConfigurationErrorKind {
AccessDeniedException(AccessDeniedException),
ConflictException(ConflictException),
InternalServerException(InternalServerException),
ServiceQuotaExceededException(ServiceQuotaExceededException),
ValidationException(ValidationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateSlackChannelConfiguration
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You don't have sufficient permission to perform this action.
ConflictException(ConflictException)
Your request has a conflict. For example, you might receive this error if you try the following:
-
Add, update, or delete a Slack channel configuration before you add a Slack workspace to your Amazon Web Services account.
-
Add a Slack channel configuration that already exists in your Amazon Web Services account.
-
Delete a Slack channel configuration for a live chat channel.
-
Delete a Slack workspace from your Amazon Web Services account that has an active live chat channel.
-
Call the
RegisterSlackWorkspaceForOrganization
API from an Amazon Web Services account that doesn't belong to an organization. -
Call the
RegisterSlackWorkspaceForOrganization
API from a member account, but the management account hasn't registered that workspace yet for the organization.
InternalServerException(InternalServerException)
We can’t process your request right now because of a server issue. Try again later.
ServiceQuotaExceededException(ServiceQuotaExceededException)
Your Service Quotas request exceeds the quota for the service. For example, your Service Quotas request to Amazon Web Services Support App might exceed the maximum number of workspaces or channels per account, or the maximum number of accounts per Slack channel.
ValidationException(ValidationException)
Your request input doesn't meet the constraints that the Amazon Web Services Support App specifies.
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.