Enum aws_sdk_dynamodb::operation::execute_transaction::ExecuteTransactionError

#[non_exhaustive]
pub enum ExecuteTransactionError {
    IdempotentParameterMismatchException(IdempotentParameterMismatchException),
    InternalServerError(InternalServerError),
    ProvisionedThroughputExceededException(ProvisionedThroughputExceededException),
    RequestLimitExceeded(RequestLimitExceeded),
    ResourceNotFoundException(ResourceNotFoundException),
    TransactionCanceledException(TransactionCanceledException),
    TransactionInProgressException(TransactionInProgressException),
    Unhandled(Unhandled),
}

Error type for the ExecuteTransactionError operation.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

IdempotentParameterMismatchException(IdempotentParameterMismatchException)

DynamoDB rejected the request because you retried a request with a different payload but with an idempotent token that was already used.

InternalServerError(InternalServerError)

An error occurred on the server side.

ProvisionedThroughputExceededException(ProvisionedThroughputExceededException)

Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically retry requests that receive this exception. Your request is eventually successful, unless your retry queue is too large to finish. Reduce the frequency of requests and use exponential backoff. For more information, go to Error Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.

RequestLimitExceeded(RequestLimitExceeded)

Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a quota increase.

ResourceNotFoundException(ResourceNotFoundException)

The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE.

TransactionCanceledException(TransactionCanceledException)

The entire transaction request was canceled.

DynamoDB cancels a TransactWriteItems request under the following circumstances:

• A condition in one of the condition expressions is not met.

• A table in the TransactWriteItems request is in a different account or region.

• More than one action in the TransactWriteItems operation targets the same item.

• There is insufficient provisioned capacity for the transaction to be completed.

• An item size becomes too large (larger than 400 KB), or a local secondary index (LSI) becomes too large, or a similar validation error occurs because of changes made by the transaction.

• There is a user error, such as an invalid data format.

• There is an ongoing TransactWriteItems operation that conflicts with a concurrent TransactWriteItems request. In this case the TransactWriteItems operation fails with a TransactionCanceledException.

DynamoDB cancels a TransactGetItems request under the following circumstances:

• There is an ongoing TransactGetItems operation that conflicts with a concurrent PutItem, UpdateItem, DeleteItem or TransactWriteItems request. In this case the TransactGetItems operation fails with a TransactionCanceledException.

• A table in the TransactGetItems request is in a different account or region.

• There is insufficient provisioned capacity for the transaction to be completed.

• There is a user error, such as an invalid data format.

If using Java, DynamoDB lists the cancellation reasons on the CancellationReasons property. This property is not set for other languages. Transaction cancellation reasons are ordered in the order of requested items, if an item has no error it will have None code and Null message.

Cancellation reason codes and possible error messages:

• No Errors:

  • Code: None

  • Message: null

• Conditional Check Failed:

  • Code: ConditionalCheckFailed

  • Message: The conditional request failed.

• Item Collection Size Limit Exceeded:

  • Code: ItemCollectionSizeLimitExceeded

  • Message: Collection size exceeded.

• Transaction Conflict:

  • Code: TransactionConflict

  • Message: Transaction is ongoing for the item.

• Provisioned Throughput Exceeded:

  • Code: ProvisionedThroughputExceeded

  • Messages:

    • The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API.

      This Message is received when provisioned throughput is exceeded is on a provisioned DynamoDB table.

    • The level of configured provisioned throughput for one or more global secondary indexes of the table was exceeded. Consider increasing your provisioning level for the under-provisioned global secondary indexes with the UpdateTable API.

      This message is returned when provisioned throughput is exceeded is on a provisioned GSI.

• Throttling Error:

  • Code: ThrottlingError

  • Messages:

    • Throughput exceeds the current capacity of your table or index. DynamoDB is automatically scaling your table or index so please try again shortly. If exceptions persist, check if you have a hot key: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-partition-key-design.html.

      This message is returned when writes get throttled on an On-Demand table as DynamoDB is automatically scaling the table.

    • Throughput exceeds the current capacity for one or more global secondary indexes. DynamoDB is automatically scaling your index so please try again shortly.

      This message is returned when writes get throttled on an On-Demand GSI as DynamoDB is automatically scaling the GSI.

• Validation Error:

  • Code: ValidationError

  • Messages:

    • One or more parameter values were invalid.

    • The update expression attempted to update the secondary index key beyond allowed size limits.

    • The update expression attempted to update the secondary index key to unsupported type.

    • An operand in the update expression has an incorrect data type.

    • Item size to update has exceeded the maximum allowed size.

    • Number overflow. Attempting to store a number with magnitude larger than supported range.

    • Type mismatch for attribute to update.

    • Nesting Levels have exceeded supported limits.

    • The document path provided in the update expression is invalid for update.

    • The provided expression refers to an attribute that does not exist in the item.

TransactionInProgressException(TransactionInProgressException)

The transaction with the given request token is already in progress.

Recommended Settings

This is a general recommendation for handling the TransactionInProgressException. These settings help ensure that the client retries will trigger completion of the ongoing TransactWriteItems request.

• Set clientExecutionTimeout to a value that allows at least one retry to be processed after 5 seconds have elapsed since the first attempt for the TransactWriteItems operation.

• Set socketTimeout to a value a little lower than the requestTimeout setting.

• requestTimeout should be set based on the time taken for the individual retries of a single HTTP request for your use case, but setting it to 1 second or higher should work well to reduce chances of retries and TransactionInProgressException errors.

• Use exponential backoff when retrying and tune backoff if needed.

Assuming default retry policy, example timeout settings based on the guidelines above are as follows:

Example timeline:

• 0-1000 first attempt

• 1000-1500 first sleep/delay (default retry policy uses 500 ms as base delay for 4xx errors)

• 1500-2500 second attempt

• 2500-3500 second sleep/delay (500 * 2, exponential backoff)

• 3500-4500 third attempt

• 4500-6500 third sleep/delay (500 * 2^2)

• 6500-7500 fourth attempt (this can trigger inline recovery since 5 seconds have elapsed since the first attempt reached TC)

Unhandled(Unhandled)

👎Deprecated: Matching Unhandled directly is not forwards compatible. Instead, match using a variable wildcard pattern and check .code():    err if err.code() == Some("SpecificExceptionCode") => { /* handle the error */ } See ProvideErrorMetadata for what information is available for the error.

An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).

Implementations

impl ExecuteTransactionError

pub fn unhandled(err: impl Into<Box<dyn Error + Send + Sync + 'static>>) -> Self

Creates the ExecuteTransactionError::Unhandled variant from any error type.

pub fn generic(err: ErrorMetadata) -> Self

Creates the ExecuteTransactionError::Unhandled variant from an ErrorMetadata.

pub fn meta(&self) -> &ErrorMetadata

Returns error metadata, which includes the error code, message, request ID, and potentially additional information.

pub fn is_idempotent_parameter_mismatch_exception(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::IdempotentParameterMismatchException.

pub fn is_internal_server_error(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::InternalServerError.

pub fn is_provisioned_throughput_exceeded_exception(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::ProvisionedThroughputExceededException.

pub fn is_request_limit_exceeded(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::RequestLimitExceeded.

pub fn is_resource_not_found_exception(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::ResourceNotFoundException.

pub fn is_transaction_canceled_exception(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::TransactionCanceledException.

pub fn is_transaction_in_progress_exception(&self) -> bool

Returns true if the error kind is ExecuteTransactionError::TransactionInProgressException.

Trait Implementations

impl CreateUnhandledError for ExecuteTransactionError

fn create_unhandled_error( source: Box<dyn Error + Send + Sync + 'static>, meta: Option<ErrorMetadata>, ) -> Self

Creates an unhandled error variant with the given source and error metadata.

impl Debug for ExecuteTransactionError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for ExecuteTransactionError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for ExecuteTransactionError

fn source(&self) -> Option<&(dyn Error + 'static)>

The lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0: use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0: replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type based access to context intended for error reports.

impl From<ExecuteTransactionError> for Error

fn from(err: ExecuteTransactionError) -> Self

Converts to this type from the input type.

impl ProvideErrorKind for ExecuteTransactionError

fn code(&self) -> Option<&str>

Returns the code for this error if one exists

fn retryable_error_kind(&self) -> Option<ErrorKind>

Returns the ErrorKind when the error is modeled as retryable

impl ProvideErrorMetadata for ExecuteTransactionError

fn meta(&self) -> &ErrorMetadata

Returns error metadata, which includes the error code, message, request ID, and potentially additional information.

fn code(&self) -> Option<&str>

Returns the error code if it’s available.

fn message(&self) -> Option<&str>

Returns the error message, if there is one.

impl RequestId for ExecuteTransactionError

fn request_id(&self) -> Option<&str>

Returns the request ID, or None if the service could not be reached.