#[non_exhaustive]
pub enum AddAttachmentsToSetErrorKind {
AttachmentLimitExceeded(AttachmentLimitExceeded),
AttachmentSetExpired(AttachmentSetExpired),
AttachmentSetIdNotFound(AttachmentSetIdNotFound),
AttachmentSetSizeLimitExceeded(AttachmentSetSizeLimitExceeded),
InternalServerError(InternalServerError),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the AddAttachmentsToSet
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AttachmentLimitExceeded(AttachmentLimitExceeded)
The limit for the number of attachment sets created in a short period of time has been exceeded.
AttachmentSetExpired(AttachmentSetExpired)
The expiration time of the attachment set has passed. The set expires 1 hour after it is created.
AttachmentSetIdNotFound(AttachmentSetIdNotFound)
An attachment set with the specified ID could not be found.
AttachmentSetSizeLimitExceeded(AttachmentSetSizeLimitExceeded)
A limit for the size of an attachment set has been exceeded. The limits are three attachments and 5 MB per attachment.
InternalServerError(InternalServerError)
An internal server error occurred.
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.