Class DynamoDbException
- Exception
-
RuntimeException
-
Aws\Exception\AwsException implements Aws\MonitoringEventsInterface, Aws\ResponseContainerInterface, ArrayAccess uses Aws\HasDataTrait, Aws\HasMonitoringEventsTrait
-
Aws\DynamoDb\Exception\DynamoDbException
- Namespace: Aws\DynamoDb\Exception
- Located at DynamoDb/Exception/DynamoDbException.php
Represents an error interacting with the Amazon DynamoDB service.
Methods Summary
Methods inherited from Aws\Exception\AwsException
__construct()
,
__toString()
,
get()
,
getAwsErrorCode()
,
getAwsErrorMessage()
,
getAwsErrorShape()
,
getAwsErrorType()
,
getAwsRequestId()
,
getCommand()
,
getRequest()
,
getResponse()
,
getResult()
,
getStatusCode()
,
getTransferInfo()
,
hasKey()
,
isConnectionError()
,
isMaxRetriesExceeded()
,
search()
,
setMaxRetriesExceeded()
,
setTransferInfo()
Methods inherited from Exception
__wakeup()
,
getCode()
,
getFile()
,
getLine()
,
getMessage()
,
getPrevious()
,
getTrace()
,
getTraceAsString()
Methods inherited from ArrayAccess
offsetExists()
,
offsetGet()
,
offsetSet()
,
offsetUnset()
Methods inherited from Aws\MonitoringEventsInterface
Methods used from Aws\HasDataTrait
Methods used from Aws\HasMonitoringEventsTrait
Expected Exception Codes
BackupInUseException
[ 'message' => '<string>', ]
Description
There is another ongoing conflicting backup control plane operation on the table. The backup is either being created, deleted or restored to a table.
Members
- message
-
- Type: string
BackupNotFoundException
[ 'message' => '<string>', ]
Description
Backup not found for the given BackupARN.
Members
- message
-
- Type: string
ConditionalCheckFailedException
[ 'Item' => [ '<AttributeName>' => [ 'B' => <string || resource || Psr\Http\Message\StreamInterface>, 'BOOL' => true || false, 'BS' => [<string || resource || Psr\Http\Message\StreamInterface>, ...], 'L' => [ [...], // RECURSIVE // ... ], 'M' => [ '<AttributeName>' => [...], // RECURSIVE // ... ], 'N' => '<string>', 'NS' => ['<string>', ...], 'NULL' => true || false, 'S' => '<string>', 'SS' => ['<string>', ...], ], // ... ], 'message' => '<string>', ]
Description
A condition specified in the operation could not be evaluated.
Members
- Item
-
- Type: Associative array of custom strings keys (AttributeName) to AttributeValue structures
Item which caused the
ConditionalCheckFailedException
. - message
-
- Type: string
The conditional request failed.
ContinuousBackupsUnavailableException
[ 'message' => '<string>', ]
Description
Backups have not yet been enabled for this table.
Members
- message
-
- Type: string
DuplicateItemException
[ 'message' => '<string>', ]
Description
There was an attempt to insert an item with the same primary key as an item that already exists in the DynamoDB table.
Members
- message
-
- Type: string
ExportConflictException
[ 'message' => '<string>', ]
Description
There was a conflict when writing to the specified S3 bucket.
Members
- message
-
- Type: string
ExportNotFoundException
[ 'message' => '<string>', ]
Description
The specified export was not found.
Members
- message
-
- Type: string
GlobalTableAlreadyExistsException
[ 'message' => '<string>', ]
Description
The specified global table already exists.
Members
- message
-
- Type: string
GlobalTableNotFoundException
[ 'message' => '<string>', ]
Description
The specified global table does not exist.
Members
- message
-
- Type: string
IdempotentParameterMismatchException
[ 'Message' => '<string>', ]
Description
DynamoDB rejected the request because you retried a request with a different payload but with an idempotent token that was already used.
Members
- Message
-
- Type: string
ImportConflictException
[ 'message' => '<string>', ]
Description
There was a conflict when importing from the specified S3 source. This can occur when the current import conflicts with a previous import request that had the same client token.
Members
- message
-
- Type: string
ImportNotFoundException
[ 'message' => '<string>', ]
Description
The specified import was not found.
Members
- message
-
- Type: string
IndexNotFoundException
[ 'message' => '<string>', ]
Description
The operation tried to access a nonexistent index.
Members
- message
-
- Type: string
InternalServerError
[ 'message' => '<string>', ]
Description
An error occurred on the server side.
Members
- message
-
- Type: string
The server encountered an internal error trying to fulfill the request.
InvalidExportTimeException
[ 'message' => '<string>', ]
Description
The specified ExportTime
is outside of the point in time recovery window.
Members
- message
-
- Type: string
InvalidRestoreTimeException
[ 'message' => '<string>', ]
Description
An invalid restore time was specified. RestoreDateTime must be between EarliestRestorableDateTime and LatestRestorableDateTime.
Members
- message
-
- Type: string
ItemCollectionSizeLimitExceededException
[ 'message' => '<string>', ]
Description
An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.
Members
- message
-
- Type: string
The total size of an item collection has exceeded the maximum limit of 10 gigabytes.
LimitExceededException
[ 'message' => '<string>', ]
Description
There is no limit to the number of daily on-demand backups that can be taken.
For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include CreateTable
, UpdateTable
, DeleteTable
,UpdateTimeToLive
, RestoreTableFromBackup
, and RestoreTableToPointInTime
.
When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.
There is a soft account quota of 2,500 tables.
GetRecords was called with a value of more than 1000 for the limit request parameter.
More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling.
Members
- message
-
- Type: string
Too many operations for a given subscriber.
PointInTimeRecoveryUnavailableException
[ 'message' => '<string>', ]
Description
Point in time recovery has not yet been enabled for this source table.
Members
- message
-
- Type: string
ProvisionedThroughputExceededException
[ 'message' => '<string>', ]
Description
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.
Members
- message
-
- Type: string
You exceeded your maximum allowed provisioned throughput.
ReplicaAlreadyExistsException
[ 'message' => '<string>', ]
Description
The specified replica is already part of the global table.
Members
- message
-
- Type: string
ReplicaNotFoundException
[ 'message' => '<string>', ]
Description
The specified replica is no longer part of the global table.
Members
- message
-
- Type: string
RequestLimitExceeded
[ 'message' => '<string>', ]
Description
Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a quota increase.
Members
- message
-
- Type: string
ResourceInUseException
[ 'message' => '<string>', ]
Description
The operation conflicts with the resource's availability. For example, you attempted to recreate an existing table, or tried to delete a table currently in the CREATING
state.
Members
- message
-
- Type: string
The resource which is being attempted to be changed is in use.
ResourceNotFoundException
[ 'message' => '<string>', ]
Description
The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE
.
Members
- message
-
- Type: string
The resource which is being requested does not exist.
TableAlreadyExistsException
[ 'message' => '<string>', ]
Description
A target table with the specified name already exists.
Members
- message
-
- Type: string
TableInUseException
[ 'message' => '<string>', ]
Description
A target table with the specified name is either being created or deleted.
Members
- message
-
- Type: string
TableNotFoundException
[ 'message' => '<string>', ]
Description
A source table with the name TableName
does not currently exist within the subscriber's account or the subscriber is operating in the wrong Amazon Web Services Region.
Members
- message
-
- Type: string
TransactionCanceledException
[ 'CancellationReasons' => [ [ 'Code' => '<string>', 'Item' => [ '<AttributeName>' => [ 'B' => <string || resource || Psr\Http\Message\StreamInterface>, 'BOOL' => true || false, 'BS' => [<string || resource || Psr\Http\Message\StreamInterface>, ...], 'L' => [ [...], // RECURSIVE // ... ], 'M' => [ '<AttributeName>' => [...], // RECURSIVE // ... ], 'N' => '<string>', 'NS' => ['<string>', ...], 'NULL' => true || false, 'S' => '<string>', 'SS' => ['<string>', ...], ], // ... ], 'Message' => '<string>', ], // ... ], 'Message' => '<string>', ]
Description
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.
DynamoDB cancels a TransactGetItems
request under the following circumstances:
-
There is an ongoing
TransactGetItems
operation that conflicts with a concurrentPutItem
,UpdateItem
,DeleteItem
orTransactWriteItems
request. In this case theTransactGetItems
operation fails with aTransactionCanceledException
. -
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.
-
-
Members
- CancellationReasons
-
- Type: Array of CancellationReason structures
A list of cancellation reasons.
- Message
-
- Type: string
TransactionConflictException
[ 'message' => '<string>', ]
Description
Operation was rejected because there is an ongoing transaction for the item.
Members
- message
-
- Type: string
TransactionInProgressException
[ 'Message' => '<string>', ]
Description
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 theTransactWriteItems
operation. -
Set
socketTimeout
to a value a little lower than therequestTimeout
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 andTransactionInProgressException
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)
Members
- Message
-
- Type: string