All Products
Search
Document Center

Tablestore:Error codes

Last Updated:May 26, 2026

Lists common Tablestore errors by category—access control, HTTP, API, and Tablestore-specific—with error codes, descriptions, and retry guidance.

Note

Errors with Retry = Yes can be resolved by retrying the request.

Access control errors

HTTP status code

Error code

Error message

Description

Retry

403

OTSAuthFailed

The AccessKey ID does not exist.

The specified AccessKey ID does not exist.

No

403

OTSAuthFailed

The AccessKey ID is disabled.

The specified AccessKey ID is disabled.

No

403

OTSAuthFailed

The user does not exist.

The specified user does not exist.

No

403

OTSAuthFailed

The instance does not exist.

The specified instance does not exist.

No

403

OTSAuthFailed

The user does not have permission to access the instance.

You do not have the required permissions to access the instance.

No

403

OTSAuthFailed

The instance is not running.

The instance is not in the Running state.

No

403

OTSAuthFailed

Signature mismatch.

The server-calculated signature does not match the signature that you provided.

No

403

OTSAuthFailed

Mismatch between system time and x-ots-date: {Date}.

The time difference between the server's clock and the time specified in the x-ots-date request header exceeds the allowed range.

No

403

OTSAuthFailed

Request denied by instance ACL policies.

The instance's network access policies block the client's network type. Handle the "Request denied by instance ACL policies" error.

No

403

OTSNoPermissionAccess

You do not have permission to access the requested resource. Contact the resource owner.

You lack permissions for this operation. Contact the resource owner to grant access. Use a RAM policy to grant permissions to a RAM user.

No

HTTP message errors

HTTP status code

Error code

Error message

Description

Retry

413

OTSRequestBodyTooLarge

The size of POST data is too large.

The POST request body exceeds the maximum allowed size.

No

408

OTSRequestTimeout

Request timeout.

The server timed out waiting for a complete request from the client.

No

405

OTSMethodNotAllowed

Only the POST method is supported.

Only POST requests are supported.

No

403

OTSAuthFailed

The MD5 value of the request body does not match the x-ots-contentmd5 header.

The MD5 value calculated from the request body does not match the value of the x-ots-content-md5 header.

No

400

OTSParameterInvalid

Missing header: {HeaderName}.

A required header is missing from the request.

No

400

OTSParameterInvalid

Invalid date format: {Date}.

The provided date string does not use a valid format.

No

400

OTSParameterInvalid

Unsupported operation: {Operation}.

The operation name in the request URL is invalid.

No

400

OTSParameterInvalid

Cannot set reserved throughput on a capacity instance.

Reserved read/write throughput cannot be set for tables in a capacity instance.

No

400

OTSForbiddenUpdateCapacityUnit

Adjusting the reserved throughput is not permitted for this instance.

Reserved read/write throughput cannot be adjusted for tables in a capacity instance.

No

API errors

HTTP status

Error code

Error message

Description

Retry

500

OTSInternalServerError

Internal server error.

Internal server error. Retry the request. If it persists, submit a ticket.

Yes

403

OTSQuotaExhausted

Table operations are too frequent.

The frequency of table operations exceeds the limit.

Yes

403

OTSQuotaExhausted

Number of tables exceeded the quota.

The number of tables exceeds the quota.

No

400

OTSParameterInvalid

Invalid instance name: {InstanceName}.

The instance name is invalid.

No

400

OTSParameterInvalid

Invalid table name: {TableName}.

The table name is invalid.

No

400

OTSParameterInvalid

Invalid column name: {ColumnName}.

The column name is invalid.

No

400

OTSParameterInvalid

{ColumnType} is an invalid type for a primary key.

The primary key column type is invalid.

No

400

OTSParameterInvalid

{ColumnType} is an invalid type for an attribute column.

The attribute column type is invalid.

No

400

OTSParameterInvalid

The number of primary key columns must be in the range: [1, {Limit}].

The number of primary key columns must be greater than zero and not exceed the limit.

No

400

OTSParameterInvalid

The value of column {ColumnName} must be UTF-8 encoded.

The column value must be UTF-8 encoded.

No

400

OTSParameterInvalid

The value of attribute column {ColumnName} is too long. The current length {CellSize} exceeds the maximum length {MaxSize}.

The value of the attribute column exceeds the size limit.

No

400

OTSParameterInvalid

No row specified in the BatchGetRow request.

No row is specified in the BatchGetRow request.

No

400

OTSParameterInvalid

Duplicate table name: {TableName}.

The BatchGetRow or BatchWriteRow operation contains duplicate table names.

No

400

OTSParameterInvalid

Duplicate primary key name: '{PKName}'.

A primary key is specified more than once.

No

400

OTSParameterInvalid

The limit must be greater than 0.

The value of the limit parameter must be greater than 0.

No

400

OTSParameterInvalid

Attribute column name conflicts with a primary key column name: {ColumnName}.

An attribute column and a primary key column have the same name.

No

400

OTSParameterInvalid

Row count exceeds the upper limit: {limit}.

The total number of rows to write exceeds the limit.

No

400

OTSParameterInvalid

Version condition not specified for the query.

The query is missing a version specification.

No

400

OTSParameterInvalid

No row is specified in BatchWriteRow.

No row data is specified in the BatchWriteRow operation.

No

400

OTSParameterInvalid

No operation is specified for table: {TableName}.

No operation is specified for the table in the BatchWriteRow operation.

No

400

OTSParameterInvalid

Invalid operation type for a row in the batch write operation.

The operation type for a row in the BatchWriteRow request is invalid. Valid types are PUT, UPDATE, or DELETE.

No

400

OTSParameterInvalid

The operation type is invalid.

The operation type in the BatchWriteRow request is invalid. Valid values: PUT, UPDATE, and DELETE.

No

400

OTSParameterInvalid

The total data size of the BatchWriteRow request ({UserSize}) exceeds the limit ({LimitSize}).

The total data size of the BatchWriteRow operation exceeds the limit.

No

400

OTSParameterInvalid

Time-to-live (TTL) is not specified.

The time to live (TTL) is not specified for the table.

No

400

OTSParameterInvalid

MaxVersions is not specified.

The max versions value is not specified for the table.

No

400

OTSParameterInvalid

Start time and end time must be specified together.

The StartTime and EndTime parameters must be specified together in the GetRange operation.

No

400

OTSParameterInvalid

Invalid column type. Only STRING, INTEGER, and BINARY are allowed.

Invalid column type. Primary key columns support only STRING, INTEGER, and BINARY types.

No

400

OTSParameterInvalid

Invalid column type: {ColumnType}.

The column type is invalid.

No

400

OTSParameterInvalid

Invalid return type: {ReturnType}.

The return type is invalid.

No

400

OTSParameterInvalid

Invalid condition: {Condition}.

The specified condition is invalid.

No

400

OTSParameterInvalid

The value of the read capacity unit cannot be less than {Limit}.

The read capacity unit cannot be less than the specified limit.

No

400

OTSParameterInvalid

The value of the write capacity unit cannot be less than {Limit}.

The write capacity unit cannot be less than the specified limit.

No

400

OTSParameterInvalid

An AUTO_INCREMENT primary key must be an integer.

Only a column of the INTEGER type can be set as an auto-increment column.

No

400

OTSParameterInvalid

The number of AUTO_INCREMENT primary keys must be 1 or less.

A maximum of one auto-increment column can be specified.

No

400

OTSParameterInvalid

Column value cannot be given when type is DELETE_ONE_VERSION,DELETE_ALL_VERSION.

You cannot specify an attribute value for a DELETE_ONE_VERSION or DELETE_ALL_VERSION operation.

No

400

OTSParameterInvalid

Timestamp must be given when type is DELETE_ONE_VERSION.

You must specify a version number when you delete a version.

No

400

OTSParameterInvalid

Timestamp cannot be given when type is DELETE_ALL_VERSION.

You cannot specify a version number when you delete all versions.

No

400

OTSParameterInvalid

No name is given for attribute column.

An attribute column name is not specified.

No

400

OTSParameterInvalid

No value is given for column name.

An attribute column value is not specified.

No

400

OTSParameterInvalid

OpType cannot be given for column name:{ColumnName} in PutRow.

Operation type can only be specified in an UpdateRow request, not in a PutRow request.

No

400

OTSParameterInvalid

Attribute column is missing.

The attribute column is missing.

No

400

OTSParameterInvalid

The number of attribute columns exceeds the limit, limit count:{Limit}, column count: {Count}.

The number of columns exceeds the limit.

No

400

OTSParameterInvalid

The length of primary key column: {ColumnName} exceeds the MaxLength: {Limit} with CurrentLength: {Current}.

The primary key length exceeds the limit.

No

400

OTSParameterInvalid

No name is given for primary key.

The primary key column name is not specified.

No

400

OTSParameterInvalid

No value is provided for the primary key name: {PkName}.

The primary key column value is not specified.

No

400

OTSParameterInvalid

OpType cannot be specified for the primary key name: {PkName}.

The operation type cannot be specified for the primary key.

No

400

OTSParameterInvalid

A Timestamp column cannot be used as a primary key: {PkName}.

A timestamp cannot be specified for the primary key.

No

400

OTSParameterInvalid

Duplicated primary key name: {PkName}.

The primary key is duplicated.

No

400

OTSParameterInvalid

Attribute column cannot be given while reading data.

The attribute column value does not need to be specified when you read data.

No

400

OTSParameterInvalid

Delete marker cannot be given.

DeleteMarker cannot be specified for a non-delete operation.

No

400

OTSParameterInvalid

The number of columns from the request exceeds the limit, limit count: {Limit} , column count:{current}.

The number of requested columns exceeds the limit.

No

400

OTSParameterInvalid

Timestamp must be in range [0, INT64_MAX/1000).

The timestamp must be greater than or equal to 0 and less than INT64_MAX/1000.

No

400

OTSParameterInvalid

TimeToLive cannot be 0 or less than -1.

The TTL cannot be 0 or less than -1, but can be -1.

No

400

OTSParameterInvalid

The maximum versions cannot be less than or equal to 0.

The maximum number of versions cannot be less than or equal to 0.

No

400

OTSParameterInvalid

Specific timestamp cannot be less than 0.

The specified timestamp cannot be less than 0.

No

400

OTSParameterInvalid

The maximum deviation must be in range [0, INT64_MAX/1000000].

The maximum version deviation must be within the valid range.

No

400

OTSParameterInvalid

Deserialize filter failed.

Failed to deserialize the filter. The filter format assembled by the SDK may be incorrect.

No

400

OTSParameterInvalid

Offset in ColumnPaginationFilter must be greater than or equal to 0.

The offset of the ColumnPaginationFilter must be greater than or equal to 0.

No

400

OTSParameterInvalid

Limit in ColumnPaginationFilter must be greater than 0.

The Limit value of the ColumnPaginationFilter must be greater than 0.

No

400

OTSParameterInvalid

Deserialize relation filter failed.

Single-column filter deserialization failed. The filter format assembled in the SDK may be incorrect.

No

400

OTSParameterInvalid

Deserialize composite filter failed.

Failed to deserialize the composite filter. The filter format assembled in the SDK may be incorrect.

No

400

OTSParameterInvalid

Deserialize column pagination filter failed.

Failed to deserialize the wide column filter. The filter format assembled in the SDK may be incorrect.

No

400

OTSParameterInvalid

The number of filters exceeds the maximum limit: {Limit}.

The number of filters exceeds the limit.

No

400

OTSParameterInvalid

Specific tiemstamp and max versions cannot be given at the same time.

A single timestamp and the maximum number of versions cannot be specified at the same time.

No

400

OTSParameterInvalid

Specific tiemstamp and time range cannot be given at the same time.

A single timestamp and a time range cannot be specified at the same time.

No

400

OTSParameterInvalid

Specific timestamp, time range and max versions cannot be given at the same time.

A single timestamp, a time range, and the maximum number of versions cannot be specified at the same time.

No

400

OTSParameterInvalid

Duplicated attribute column name with primary key column:{PkName}.

The attribute column is duplicated.

No

400

OTSParameterInvalid

The total data size of PutRow request exceeds the limit, limit size: {Limit} , data size: {Current}.

The data size in the PutRow request exceeds the limit.

No

400

OTSParameterInvalid

The total data size of UpdateRow request exceeds the limit, limit size: {Limit} , data size: {Current}.

The data size in the UpdateRow request exceeds the limit.

No

400

OTSParameterInvalid

No parameter is specified in table options.

No parameter is specified in TableOption.

No

400

OTSParameterInvalid

Input encoded PK broken, invalidate cell key type:xx.

The encoded PlainBuffer is invalid, and the cell type is incorrect.

No

400

OTSParameterInvalid

Input encoded PK broken, length is shorter than expect.

The encoded PlainBuffer is invalid, and the length is not as expected.

No

400

OTSParameterInvalid

PKAutoIncr can't be used for read operations.

The auto-increment attribute cannot be specified for read operations.

No

400

OTSParameterInvalid

Begin key must less than end key in FORWARD.

In a forward query, the start key must be less than the end key.

No

400

OTSParameterInvalid

Begin key must more than end key in BACKWARD.

In a backward query, the start key must be greater than the end key.

No

400

OTSParameterInvalid

Repeated rows do not support row exist expectation check in BatchModify.

BatchWriteRow does not support row existence condition checks for duplicate row operations.

No

400

OTSParameterInvalid

Repeated rows do not support row condition check in BatchModify.

Conditional updates are not allowed on repeated rows in a BatchWriteRow operation.

No

400

OTSParameterInvalid

PK column size not the same for all rows in table: {TableName}.

The number of primary keys in different rows is inconsistent.

No

400

OTSParameterInvalid

Duplicate rows detected in MultiPut.

Duplicate rows exist.

No

400

OTSParameterInvalid

Duplicate rows detected in MultiGet.

Duplicate rows exist.

No

400

OTSParameterInvalid

Column does not exist:{ColumnName}.

The column does not exist.

No

400

OTSParameterInvalid

Invalid max scan size: {Limit}.

The limit for range queries exceeds the limit.

No

400

OTSParameterInvalid

data format is invalid.

The PlainBuffer-encoded row data is invalid.

No

400

OTSParameterInvalid

double can not be used as primary key.

A double cannot be used in a primary key.

No

400

OTSParameterInvalid

data format is invalid, unknown variant type occured.

The PlainBuffer-encoded row data is invalid due to an illegal value type.

No

400

OTSParameterInvalid

Parse PBMessage from RawString failed.

Failed to deserialize Protobuf, possibly due to an SDK serialization code error.

No

400

OTSParameterInvalid

Cell data broken, mismatch header, actual: {Header} , expect: {Header}.

The PlainBuffer-encoded row data is invalid due to an unexpected header.

No

400

OTSParameterInvalid

Cell data broken, PK value cannot be NULL, name: {PkName}.

The PlainBuffer-encoded row data is invalid, and the value of the primary key corresponding to PkName is null.

No

400

OTSParameterInvalid

Cell data broken, PK is empty.

The PlainBuffer-encoded row data is invalid and the primary key is missing.

No

400

OTSParameterInvalid

Cell data broken, no PK follow PKTag.

The PlainBuffer-encoded row data is invalid, and the primary key content does not appear as expected after the primary key flag.

No

400

OTSParameterInvalid

Cell data broken, attr has no name.

The PlainBuffer-encoded row data is invalid and the attribute column is missing a name.

No

400

OTSParameterInvalid

Cell data broken, attr has no value, name:{Name}.

The PlainBuffer-encoded row data is invalid and the attribute column is missing a value.

No

400

OTSParameterInvalid

Cell data broken, no Cells follow CellTag.

The PlainBuffer-encoded row data is invalid, and the Cell content does not appear as expected after the Cell flag.

No

400

OTSParameterInvalid

Cell data broken, no valid element in Cell, name: {Name}.

The PlainBuffer-encoded row data is invalid, and the Cell format is garbled.

No

400

OTSParameterInvalid

Cell data broken, cell is not end with checksum[{0x0A}]"] tag.

The PlainBuffer-encoded row data is invalid, and CheckSumFlag does not appear as expected at the end of the Cell encoding.

No

400

OTSParameterInvalid

Cell data broken, row is not end with checksum tag.

The PlainBuffer-encoded row data is invalid, and CheckSumTag does not appear as expected at the end of the row data encoding.

No

400

OTSParameterInvalid

Cell data broken, mismatch tag, actual tag({TAG}), expect({TAG}).

The PlainBuffer-encoded row data is invalid, and the expected Tag does not appear.

No

400

OTSParameterInvalid

Cell data broken, wrong string format, size: {Size}.

The PlainBuffer-encoded row data is invalid due to an incorrect string encoding format.

No

400

OTSParameterInvalid

Invalid Capacity Unit for UpdateTable: Either read({CU}) or write({CU}) should be non-negative.

The read and write CUs should be greater than or equal to 0.

No

400

OTSParameterInvalid

Auto increment pk must be integer, name: {PkName}.

The auto-increment column must be of the integer type.

No

400

OTSParameterInvalid

Cannot deserialize the request data.

The data in the request cannot be deserialized, possibly due to a null value or an invalid format.

No

400

OTSParameterInvalid

Invalid row: missing checksum.

The PlainBuffer-encoded row data is invalid and the row checksum value is missing.

No

400

OTSParameterInvalid

Invalid Column({ColumnName}): missing checksum.

The PlainBuffer-encoded column data is invalid and the cell checksum value is missing.

No

400

OTSParameterInvalid

Cell data broken, checksum is mismatch, {UserChecksum}: {ServiceChecksum}

The PlainBuffer-encoded row data is invalid, and the user's UserChecksum is inconsistent with the server-calculated ServiceChecksum.

No

400

OTSParameterInvalid

Cell data broken, has more data in cell, but they can't be parsed.

The PlainBuffer-encoded column data is invalid and contains unexpectedly large amounts of data.

No

400

OTSParameterInvalid

NaN can't be set to double value.

A double type cannot be set to a NaN value.

No

400

OTSParameterInvalid

Infinity can't be set to double value.

A double type cannot be set to an Infinity value.

No

400

OTSParameterInvalid

Invalid max versions: {Version} . Reason: Max versions must be positive.

The maximum number of versions is invalid and should be greater than 0 or equal to -1.

No

400

OTSParameterInvalid

Invalid range: The start type {BeginType} does not match the end type {EndType}.

The start key type and the end key type in the range query are inconsistent.

No

400

OTSParameterInvalid

Invalid offset of Filter: {Filter} . Reason: Offset must be nonnegative.

The offset in the filter must be greater than or equal to 0.

No

400

OTSParameterInvalid

Invalid Capacity Unit:{CU} . Capacity Unit must be nonnegative.

The CU value must be greater than or equal to 0.

No

400

OTSParameterInvalid

Unknown or unsupported CellType in primary key: {PkName}.

The Cell type of the primary key cannot be identified.

No

400

OTSParameterInvalid

Invalid boolean real value, value length: {Length}.

The PlainBuffer-encoded column data is invalid, and the value length of the Bool type is invalid.

No

400

OTSParameterInvalid

invalid name of column: empty name.

The attribute column name cannot be empty.

No

400

OTSParameterInvalid

Invalid ModifyType:{ModifyType}.

The update type is invalid.

No

400

OTSParameterInvalid

Invalid relation operator: {Operation}.

The relationship operator is invalid.

No

400

OTSParameterInvalid

Invalid type of filter: {Type}.

The filter type is invalid.

No

400

OTSParameterInvalid

Invalid NOT operator: the number of sub-filters must be 1.

The NOT operator allows only one subfilter.

No

400

OTSParameterInvalid

Invalid AND/OR operator: the number of sub-filters must be 2.

The AND/OR operators require only two subfilters.

No

400

OTSParameterInvalid

Invalid type of sub-filter: {Filter}.

The subfilter type is invalid.

No

400

OTSParameterInvalid

{Count} pk auto increment exist in row.

Multiple PK auto-increment columns exist.

No

400

OTSParameterInvalid

Invalid action: {Action}.

Invalid action type.

No

400

OTSParameterInvalid

Invalid row-existence expectation: {Expectation}.

The specified row existence condition is invalid.

No

400

OTSParameterInvalid

Invalid row to delete which with pk auto increment.

The auto-increment column attribute cannot be set upon deletion.

No

400

OTSParameterInvalid

Invalid expect:{RowExpect} when modify row with pk auto increment.

The row existence condition specified when using a primary key auto-increment column is invalid.

No

400

OTSParameterInvalid

Can't set condition when modify row with pk auto increment.

ConditionUpdate cannot be set when using a primary key auto-increment column.

No

400

OTSParameterInvalid

Invalid expect: {RowExpect} when modify a specific row for table with pk auto increment.

The specified row existence condition is invalid when modifying a specific row in a primary key auto-increment table.

No

400

OTSParameterInvalid

Invalid cell: {Cell}. missing timestamp.

Missing timestamp.

No

400

OTSParameterInvalid

Invalid cell timestamp: {Timestamp}. Expect: [0, Version::kMax.mVersion / kUsecPerMsec]..

The specified timestamp is invalid.

No

400

OTSParameterInvalid

Invalid timestamp. Cell:{CellName}.

Data can be written successfully only when the specified timestamp (in milliseconds) is divided by 1000 and converted to seconds in the valid version range [max{data write time-valid version deviation, data write time-data lifecycle}, data write time+valid version deviation).

No

400

OTSParameterInvalid

Invalid timestamp for cell: {Timestamp}. timestamp is inapplicable to DELETE_ALL_VERSION.

When you use DELETE_ALL_VERSION to delete all versions, you cannot specify a version.

No

400

OTSParameterInvalid

Invalid op type of cell: {OpType}.

Invalid action type.

No

400

OTSParameterInvalid

Invalid cell: {Cell}. Reason: missing value.

Invalid Cell, missing value.

No

400

OTSParameterInvalid

Invalid request of delete row: missing RowDeleteMarker in request.

RowDeleteMarker is missing from the delete request.

No

400

OTSParameterInvalid

Invalid request of put/update row: unexpected RowDeleteMarker in request.

PutRow and UpdateRow cannot contain RowDeleteMarker.

No

400

OTSParameterInvalid

Invalid update row request: missing cells in request.

An attribute column value is missing from UpdateRow.

No

400

OTSParameterInvalid

Invalid delete row request: unexpected cells in request.

The attribute column value should not appear in DeleteRow.

No

400

OTSParameterInvalid

Invalid request of put row: find cells without values.

An attribute column value is missing from PutRow.

No

400

OTSParameterInvalid

Can not reserve read capacity unit on hybrid storage cluster: {TableName}.

You cannot set reserved read CUs for a hybrid storage instance.

No

400

OTSParameterInvalid

Can not reserve write capacity unit on hybrid storage cluster: {TableName}.

You cannot set reserved write CUs for a hybrid storage instance.

No

400

OTSParameterInvalid

First primary key can't be auto increment, table: {TableName}.

The first primary key cannot be set as an auto-increment column.

No

400

OTSParameterInvalid

PkAutoIncr cannot be set as first pk column.

An auto-increment column cannot be set as the first primary key column.

No

400

OTSParameterInvalid

the count of auto-incremental primary keys can not be more than 1.

The number of auto-increment columns cannot exceed 1.

No

400

OTSParameterInvalid

Can't write index table directly.

Write operations on index tables are not allowed.

No

400

OTSParameterInvalid

Try to call method using explicit transaction on explicit-transaction-disabled table.

The table does not have local transactions enabled.

No

400

OTSParameterInvalid

Table[tablename] who has at least one search index cannot be deleted.

A table that has an index cannot be deleted.

No

400

OTSParameterInvalid

nested field aggregation/groupby must not be recursive.

Multi-level GroupBy or Aggregation cannot be used in nested fields.

No

400

OTSParameterInvalid

The number of defined columns must be in range: [0, 32].

The number of predefined columns cannot exceed 32.

No

400

OTSParameterInvalid

failed to query index, please check if 'Index' is enabled for query fields.

The query field is not indexed.

No

400

OTSParameterInvalid

[table ttl] must be bigger than or equal search index ttl, but table ttl is xxxx and search index ttl is [{IndexName}:xxxx]

The TTL of the data table must be greater than or equal to the TTL of the search index.

No

400

OTSParameterInvalid

the number of index in creating has exceed the instance quota, limit: 10

For resource considerations, the cumulative number of search indexes with dynamically modified schemas and regular search indexes being created cannot exceed 10. Please wait for the indexes being created to finish synchronizing before creating more.

No

400

OTSParameterInvalid

can't delete analytical store with sql binding

You cannot delete an analytical store bound to an SQL mapping table. Delete the SQL mapping table first.

No

400

OTSInvalidPK

Primary key schema mismatch.

The primary key does not match.

No

400

OTSOutOfRowSizeLimit

The total data size of columns in one row exceeded the limit.

The total data size of all columns in this row exceeds the limit.

No

400

OTSOutOfColumnCountLimit

The number of columns in one row exceeded the limit.

The total number of columns in this row exceeds the limit.

No

400

OTSTunnelServerUnavailable

OTSTrimmedDataAccess Requested stream data is already trimmed or does not exist.

The stream log has expired and data has not been pulled for a long time.

No

Tablestore-related errors

HTTP status

Error code

Error message

Description

Retry

503

OTSServerBusy

Server is busy.

An internal Tablestore server is busy. The operation may succeed on retry.

Yes

503

OTSPartitionUnavailable

The partition is not available.

This error typically occurs while a partition is loading. Retry after a brief delay.

Yes

503

OTSTimeout

Operation timeout.

An internal Tablestore operation timed out.

Yes

503

OTSServerUnavailable

Server is not available.

An internal Tablestore server is inaccessible.

Yes

409

OTSRowOperationConflict

Another request is modifying the data.

This error occurs when concurrent write requests to the same row conflict.

Yes

409

OTSObjectAlreadyExist

Requested table already exists.

The specified data table or index table already exists.

No

404

OTSObjectNotExist

Requested table does not exist.

The specified table does not exist.

No

404

OTSTableNotReady

The table is not ready.

The table is initializing after creation. The operation may succeed if you retry in a few seconds.

Yes

403

OTSTooFrequentReserved ThroughputAdjustment

Capacity unit adjustments are too frequent.

Adjustments to the read or write capacity units are too frequent.

Yes

403

OTSCapacityUnitExhausted

Insufficient capacity units.

The provisioned read or write capacity units for the data partition are exhausted.

No

403

OTSConditionCheckFail

Condition check failed.

The specified condition for the operation was not met.

No

429

OTSFlowControl

Request rate limit exceeded.

Analyze the error based on your specific use case. If the issue persists, submit a ticket to contact Tablestore technical support.

No