class Aws::DynamoDB::Types::TransactionInProgressException

@see docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10/TransactionInProgressException AWS API Documentation
@return [String]
@!attribute [rw] message<br><br>: github.com/aws/aws-sdk-java/blob/fd409dee8ae23fb8953e0bb4dbde65536a7e0514/aws-java-sdk-core/src/main/java/com/amazonaws/retry/PredefinedRetryPolicies.java#L97<br><br><br><br>seconds have elapsed since the first attempt reached TC)
* 6500-7500 fourth attempt (this can trigger inline recovery since 5
* 4500-6500 third sleep/delay (500 * 2^2)
* 3500-4500 third attempt
* 2500-3500 second sleep/delay (500 * 2, exponential backoff)
* 1500-2500 second attempt
base delay for 4xx errors)
* 1000-1500 first sleep/delay (default retry policy uses 500 ms as
* 0-1000 first attempt
Example timeline:
the guidelines above are as follows:
Assuming [default retry policy], example timeout settings based on
* Use exponential backoff when retrying and tune backoff if needed.
of retries and ‘TransactionInProgressException` errors.
setting it to 1 second or higher should work well to reduce chances
individual retries of a single HTTP request for your use case, but
* `requestTimeout` should be set based on the time taken for the
`requestTimeout` setting.
* Set `socketTimeout` to a value a little lower than the
attempt for the `TransactWriteItems` operation.
retry to be processed after 5 seconds have elapsed since the first
* Set `clientExecutionTimeout` to a value that allows at least one
</note>
`TransactWriteItems` request.
client retries will trigger completion of the ongoing
`TransactionInProgressException`. These settings help ensure that the
<note markdown=“1”> This is a general recommendation for handling the
Recommended Settings
The transaction with the given request token is already in progress.