class Aws::DynamoDB::Types::TransactionCanceledException

@see docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10/TransactionCanceledException AWS API Documentation
@return [Array<Types::CancellationReason>]
A list of cancellation reasons.
@!attribute [rw] cancellation_reasons
@return [String]
@!attribute [rw] message
exist in the item.
* The provided expression refers to an attribute that does not
for update.
* The document path provided in the update expression is invalid
* Nesting Levels have exceeded supported limits.
* Type mismatch for attribute to update.
larger than supported range.
* Number overflow. Attempting to store a number with magnitude
* Item size to update has exceeded the maximum allowed size.
* An operand in the update expression has an incorrect data type.
key to unsupported type.
* The update expression attempted to update the secondary index
key beyond allowed size limits.
* The update expression attempted to update the secondary index
* One or more parameter values were invalid.
* Messages:
* Code: ‘ValidationError`
* Validation Error:
</note>
On-Demand GSI as DynamoDB is automatically scaling the GSI.
<note markdown=“1”> This message is returned when when writes get throttled on an
so please try again shortly.
secondary indexes. DynamoDB is automatically scaling your index
* Throughput exceeds the current capacity for one or more global
</note>
On-Demand table as DynamoDB is automatically scaling the table.
<note markdown=“1”> This message is returned when writes get throttled on an
.
hot key:
try again shortly. If exceptions persist, check if you have a
DynamoDB is automatically scaling your table or index so please
* Throughput exceeds the current capacity of your table or index.
* Messages:
* Code: `ThrottlingError`
* Throttling Error:
</note>
is on a provisioned GSI.
<note markdown=“1”> This message is returned when provisioned throughput is exceeded
global secondary indexes with the UpdateTable API.
increasing your provisioning level for the under-provisioned
global secondary indexes of the table was exceeded. Consider
* The level of configured provisioned throughput for one or more
</note>
is on a provisioned DynamoDB table.
<note markdown=“1”> This Message is received when provisioned throughput is exceeded
UpdateTable API.
exceeded. Consider increasing your provisioning level with the
* The level of configured provisioned throughput for the table was
* Messages:
* Code: `ProvisionedThroughputExceeded`
* Provisioned Throughput Exceeded:
* Message: Transaction is ongoing for the item.
* Code: `TransactionConflict`
* Transaction Conflict:
* Message: Collection size exceeded.
* Code: `ItemCollectionSizeLimitExceeded`
* Item Collection Size Limit Exceeded:
* Message: The conditional request failed.
* Code: `ConditionalCheckFailed`
* Conditional Check Failed:
* Message: `null`
* Code: `NONE`
* No Errors:
Cancellation reason codes and possible error messages:
</note>
and `Null` message.
of requested items, if an item has no error it will have `NONE` code
languages. Transaction cancellation reasons are ordered in the order
`CancellationReasons` property. This property is not set for other
<note markdown=“1”> If using Java, DynamoDB lists the cancellation reasons on the
* There is a user error, such as an invalid data format.
completed.
* There is insufficient provisioned capacity for the transaction to be
or region.
* A table in the `TransactGetItems` request is in a different account
operation fails with a `TransactionCanceledException`.
`TransactWriteItems` request. In this case the `TransactGetItems`
a concurrent `PutItem`, `UpdateItem`, `DeleteItem` or
* There is an ongoing `TransactGetItems` operation that conflicts with
circumstances:
DynamoDB cancels a `TransactGetItems` request under the following
* There is a user error, such as an invalid data format.
error occurs because of changes made by the transaction.
secondary index (LSI) becomes too large, or a similar validation
* An item size becomes too large (larger than 400 KB), or a local
completed.
* There is insufficient provisioned capacity for the transaction to be
the same item.
* More than one action in the `TransactWriteItems` operation targets
account or region.
* A table in the `TransactWriteItems` request is in a different
* A condition in one of the condition expressions is not met.
circumstances:
DynamoDB cancels a `TransactWriteItems` request under the following
The entire transaction request was canceled.