Error codes

Updated at:

If a request fails, an error code and an error message are returned. You can use this topic to identify the cause of the error and correct it promptly so that your requests are processed as expected.

Common errors and solutions

Error code

Solution

1000

This error is usually caused by a timeout. Retry the request and check whether the error persists. If the error persists, submit a ticket. The on-duty staff will troubleshoot the issue as soon as possible.

2112

This error is reported if the fields used in business sorting are not all included in the index fields. However, the search results are not affected.

3007

The system limits the frequency of API pushes. Control the push frequency and retry.

4003

First, follow the example in the documentation to check whether your signature result matches, which helps determine whether the issue is caused by the signature algorithm. If it is not, check whether the parameters, after being sorted in lexicographical order, place the common parameters (uppercase letters) before the request parameters (lowercase letters). Also note encoding rules such as those for spaces. For more information, see the authorization documentation.

4007

JSON parsing usually fails if the content of a JSON field contains double quotation marks or invisible characters. Escape or filter out these characters and retry.

4010

The TimeStamp parameter has an expiration time. Use the current time in the required format to calculate the value.

5001

No matching user is found. This is usually because the AccessKey information is incorrect or the domain name of the wrong region is used (the API domain name must be the one displayed in Application Management > Basic Information > API Endpoint). Check and correct the information, and then retry.

5008

The service verifies user identities by using AccessKey pairs. Make sure that your AccessKey pair is enabled. You can create and delete AccessKey pairs in the AccessKey management section of the console.

6013

The value of start+hit cannot exceed 5000. Otherwise, an error is reported and no results are returned. If your request requires more than 5,000 results, check whether the SCROLL operation described in the API documentation meets your requirements.

6015

Requests are discarded because the computing resources (LCUs) exceed the purchased quota. Log on to the console and click "Scale In/Out / Change Specifications" on the application list page to scale out the application.

6127

Except for the query clause, all fields that appear in other clauses must be configured as attribute fields before they can be used. Modify the application schema and retry. (You can configure attribute fields by using offline changes.)

7500

An internal system error occurred. If this error is reported, submit a ticket. We will troubleshoot the issue as soon as possible.

System-level errors (1000-1999)

Error code

Description

1000

An internal system error occurred.

1001

The template is not found.

1003

The index type is not supported.

1004

The service is temporarily unavailable. Try again later.

Application-related errors (2000-2999)

Error code

Description

2001

The application to be queried does not exist.

2002

The application already exists.

2003

The maximum number of applications that can be created has been reached.

2004

The application name is invalid. The application name can contain digits, letters, and underscores (_), and can be up to 30 characters in length.

2005

The application name is not specified.

2006

The new application name is not specified.

2007

The description cannot exceed 300 characters.

2008

The summary configuration parameters are invalid.

2009

Failed to update the status.

2010

The application is suspended.

2011

The application is frozen.

2012

The application is not enabled.

2013

Deletion failed because the application does not exist.

2014

Failed to upload the file.

2016

The region information is missing.

2017

The application does not belong to the current region.

2099

The current operation is temporarily unavailable.

2101

The expression does not exist.

2102

The expression name is already in use.

2103

The maximum number of expressions for the application has been reached.

2104

The expression name is invalid. The expression name can contain digits, letters, and underscores (_), and can be up to 30 characters in length.

2105

The expression name is not specified.

2106

The new expression name is not specified.

2107

The expression description cannot exceed 300 characters.

2108

The format of the expression description is invalid.

2109

The format of the expression is invalid.

2110

The length of the expression exceeds the limit.

2111

The expression ID is not specified.

2112

The expression is invalid.

2113

The expression cannot be empty.

2114

Operation error.

2201

The name of the rough sort configuration is not specified.

2202

The name of the rough sort configuration already exists.

2203

The number of rough sort configurations exceeds the limit.

2204

The name of the rough sort configuration is invalid. The name can contain only digits, letters, and underscores (_).

2205

The length of the rough sort configuration name exceeds the limit.

2206

Rough sort fields must be of a numeric type.

2207

The rough sort configuration does not exist.

2208

The rough sort configuration is invalid. It must contain fields.

2209

The weight in the rough sort configuration is invalid. The weight must be a non-zero value from -100000 to 100000. Floating-point numbers support a precision of up to 6 digits.

2210

The name is the same as that of the default rough sort configuration of the system.

2211

The parameter of timeliness() must be of the INT type.

2112

The sort expression is invalid.

2551

The specified drop-down suggestion rule does not exist.

Document-related errors (3000-3999)

Error code

Description

3001

The document cannot be empty.

3002

The document size exceeds the limit.

3003

The maximum number of documents has been reached.

3004

Failed to save the document.

3005

The doc format is invalid.

3006

The document operation cmd is invalid.

3007

Requests are too frequent.

3008

The total length of the documents is too long.

3009

The document ID is missing.

3011

After an RDS or MySQL data source is configured, documents cannot be pushed by using API operations.

3012

The specified resource is not found.

3013

The document push rate exceeds the application quota.

3014

The document push rate triggers the system limit.

3015

The number of documents pushed at a time exceeds the system limit.

3016

The total number of documents exceeds the application quota.

Authorization-related errors (4000-4999)

Error code

Description

4001

Authentication failed.

4002

A signature is required.

4003

Signature verification failed.

4004

SignatureNonce is required.

4005

SignatureNonce cannot be reused.

4006

SignatureNonce verification failed.

4007

Failed to parse the JSON format.

4008

The username cannot be empty. Check whether the domain name is correct.

4009

A user identifier must be specified.

4010

The time has expired.

4011

The operation is not allowed for demo accounts.

4012

The data table does not exist.

4013

The Timestamp format is invalid.

4014

Timestamp is required.

4020

Authentication of the RAM user failed.

User-related errors (5000-5999)

Error code

Description

5001

The user does not exist.

5002

The username is incorrect.

5003

The user must log on.

5008

The user has not enabled an AccessKey pair.

5100

The user does not have operation permissions in this region.

5004

The user has not paid.

5005

The user has not activated OpenSearch. Go to the Alibaba Cloud official website to activate the service.

5006

The account is frozen due to overdue payments.

5008

The user has not enabled an AccessKey pair.

5009

The user has been deleted.

5010

The AccessKey pair has been disabled.

5011

Multiple users are found by the email address.

5012

CODE_USER_ALIYUN_USER_ID_INVALID. The error message is empty.

5013

CODE_USER_ALIYUN_BID_INVALID. The error message is empty.

5014

CODE_USER_CLIENT_ID_INVALID. The error message is empty.

5015

CODE_USER_ID_INVALID. The error message is empty.

5100

The user does not have operation permissions in this region.

Search-related errors (6000-6999)

Error code

Description

6001

The query is empty.

6002

The search keyword key is not supported.

6003

The search keyword field is not supported.

6004

The complex query is empty.

6005

The field is invalid.

6006

The request contains too many application names.

6007

The total number of indexes in each template for multi-index queries is exceeded.

6008

The request string contains syntax errors and failed to be parsed.

6009

The query clause is too long.

  • If the length of the OpenSearch query clause cannot meet your requirements, consider using the filter clause, which has a higher length limit. The length limit of the filter clause is 4 KB.

  • You can use a composite index, which allows you to configure multiple fields of the TEXT or SHORT_TEXT type in the same index.

6010

The rerank size is invalid.

6011

The SignatureNonce format is invalid.

6013

The value of start+hit exceeds the system limit.

6014

The request is discarded because the system is busy.

6015

The request is discarded because the search computing resources (LCUs) exceed the quota.

6016

The number of hits in the query exceeds the system limit.

6017

Currently, scroll supports only the scan value of search_type. That is, if you set the scroll parameter, you must also set search_type=scan.

6018

The scroll parameter is set but the search_type parameter is missing.

6019

Failed to parse the specified scroll_id parameter.

6020

The value of the scroll parameter is invalid.

6021

Scroll requests do not support Aggregate, Sort, or Distinct. An error is reported if these clauses are specified.

6022

The scroll_id has expired.

6024

The value of the hit parameter for drop-down suggestions is invalid.

6031

The value of the abtest parameter is invalid.

6033

The value of the re_search parameter is invalid.

6034

The value of the biz parameter is invalid.

6100

The query term is empty.

6101

The index field to be queried does not exist.

6102

The numeric range in the query is invalid.

6103

The return value of the expression in Filter must be of the bool type.

6104

The return value of the expression in Sort cannot be of the bool type.

6105

Sort contains identical expressions.

6106

The query statement is invalid.

6107

The return value of the aggregate function expression cannot be of the bool or string type.

6108

The ranges in aggregation must be in ascending order.

6109

The return value type of the range expression in aggregation is invalid.

6110

The aggregate function does not exist.

6111

The aggregate function is not supported.

6112

The Query clause is invalid.

6113

The Filter clause is invalid.

6114

The Aggregate clause is invalid.

6115

The Sort clause is invalid.

6116

The Distinct clause is invalid.

6117

The query contains an unknown clause.

6118

Syntax error.

6119

The dist_count value in the Distinct clause is invalid. It must be an integer greater than 0.

6120

The dist_times value in the Distinct clause is invalid. It must be an integer greater than 0.

6121

The reserved value in the Distinct clause is invalid. It must be true or false.

6122

The Distinct clause is missing distinct_key.

6123

The grade value in the Distinct clause is invalid. For example, it is empty or non-numeric.

6124

The number of distinct items in the Distinct clause is invalid. The number must be within (0,2].

6125

The max_item_count value in the Distinct clause is invalid. It must be an integer greater than 0.

6126

The update_total_hit value in the Distinct clause is invalid. It must be true or false.

6127

The request contains an undefined attribute field. Modify the application schema and retry. (You can configure attribute fields by using offline changes.)

6128

The result types of the expressions on both sides of a binary operator do not match.

6129

The expressions on both sides of a binary operator cannot both be constants.

6130

The type of the binary logical expression is invalid. It must be of the bool type.

6131

The string type is not supported in binary expressions.

6132

Array types are not supported in binary expressions.

6133

The type in the bitwise operation is invalid.

6134

The return value type of the constant expression is invalid.

6135

The type of the constant expression is invalid. Field values of the LITERAL type must be enclosed in double quotation marks in the filter clause. Otherwise, this error is reported.

6140

Aggregate clause syntax error,

Fields of the LITERAL type do not support SUM.

6300

The type of the constant expression must be integer or floating-point.

6301

The operand of bitwise NOT must be an integer.

6302

The operand of negation must be a numeric value.

6303

The operand of logical NOT must be a numeric value.

6304

The operand type of the binary operation is invalid.

6305

The binary operator is invalid.

6306

The function parameter type is invalid.

6307

The function is not defined.

6308

The number of function parameters is invalid.

6309

The array operation is invalid.

6310

The filterable field does not exist.

6311

An array field is incorrectly used as a single-value field.

6312

A single-value field is incorrectly used as an array.

6313

The array field index is out of bounds (less than 0).

6314

The field type is not supported.

6315

The index field parameter does not exist.

6316

No index is specified in the query.

6317

A formula can be used only once in the Filter clause.

6318

Failed to parse the formula syntax.

6400

The sort script does not exist.

6450

An exception occurred while the script was executed.

6500

The search syntax contains a field that does not exist.

6501

The online system has no index data.

6502

The user query has a syntax error.

6503

The default operator OR is not supported.

6504

Exact aggregation is not supported.

6505

The rank size is invalid.

6506

The query contains too many terms after tokenization.

6601

An index field can be included in only one rule.

6602

The query term is missing, such as in default:''.

6603

The index field in the query is not specified in the query analysis rule.

6604

The keyword is not enclosed in quotation marks, such as default:xxx. The correct format is default:'xxx'.

6605

Query analysis rules cannot be configured for queries enclosed in double quotation marks.

6606

Informational error: The query does not contain indexes that require query analysis.

6607

The format of the disable parameter is invalid.

6608

The index field specified to be disabled by the disable parameter does not exist.

6609

The feature list specified to be disabled by the disable parameter does not exist.

6610

The query is empty after query analysis (the original query is empty or consists entirely of stopwords).

6611

No index field is specified in the query.

6612

term_weight makeup data fail. The intervention data did not take effect.

6613

The number of terms in the query clause exceeds the upper limit of 256.

Data processing-related errors (7000-7999)

Error code

Description

7202

The cmd is not supported. The command is not supported, such as a cmd other than update, add, or delete.

7301

The document primary key field does not exist. The document primary key does not exist, and the push failed.

7302

The target type does not match. The document primary key is invalid, and the push failed.

7303

The document primary key has multiple values. The document primary key value does not support multi-value types, and the push failed.

7304

The document primary key field is empty. The document primary key value is empty, and the push failed.

7305

A table that does not belong to this application was pushed. The document table name does not exist, and the push failed.

7500

An internal system error occurred. If this error is reported, submit a ticket. We will troubleshoot the issue as soon as possible.

7520

The size of a single document exceeds 1 MB. The single document is too long and exceeds the system limit, and the push failed.

7503

The content of the field corresponding to the JSON plug-in is not JSON. The content of the JSON plug-in field is not in JSON format, and the push failed. Check the content and retry.

7504

The key corresponding to the content of the JSON plug-in field does not exist, and the push failed.

7505

An error occurred in the TairLDB plug-in. The content conversion configuration of TairLDBExtractor is invalid: Failed to connect to Tair. Check whether configId or namespace is valid.

7510

The keyvalue plug-in (KeyValueExtractor) failed to process the field, and the push failed.

7515

An error occurred while the filter condition was executed.

7523

An error occurred in the StringConnector plug-in, and the push failed.

7524

The content of the geo field is out of range. The content of the range field exceeds the longitude and latitude range (lon>180; lat>90).

7525

The format of the geo field is invalid. The content format of the range field is incorrect.

7601

An error occurred while the task was executed. If this error is reported, submit a ticket. We will troubleshoot the issue as soon as possible.

7602

The ODPS table contains 0 data records. Confirm that the ODPS partition is generated as expected and retry.

7607

No ODPS permissions.

7603

The MySQL data source (RDS/PolarDB) is incorrectly configured.

7605

TDDL configuration error

7608

Source fields are missing from the MySQL data source

7803

Failed to push data because the document to be updated does not exist

7805

Failed to push data because an error occurred while the HTML plug-in processed the data

7807

The field type does not match the field content and the conversion to the destination type failed. A default value will be used for the field

73106

The push quota is exceeded. Scale out the application

7620

The data source query timed out

Internal notifications of document errors (8000-8999)

Error code

Description

8001

Failed to save the error information

8002

Required parameters are missing

8003

The application does not exist

8004

Parameter error

Template-related errors (9000-9999)

Error code

Description

9001

The username is empty

9002

The application name is empty

9003

The template name is invalid. The template name can contain only digits, letters, and underscores (_)

9004

The template name cannot exceed 30 characters in length

9005

An error occurred while querying the template information

9006

The template name already exists

9007

An error occurred while inserting the template information

9008

Invalid data

9009

The number of defined fields exceeds the maximum number of fields allowed by the system

9010

This field name is reserved

9011

The field already exists

9012

The index name must start with a letter, can contain only digits, letters, and underscores (_), and cannot exceed 30 characters in length. The type of a multi-value field cannot be SWS_TEXT or TEXT

9013

Arrays are not supported

9014

Primary keys are not supported

9015

No primary key is specified

9016

The primary key is not unique

9017

Failed to update the information

9018

Failed to delete the information

9019

A maximum of four search fields can each contain multiple index fields

9020

An index field of the STRING or TEXT type cannot be included in multiple search fields that each contain only one field

9021

The index name must start with a letter, can contain only digits, letters, and underscores (_), and cannot exceed 30 characters in length

9022

The table is already associated

9023

An index cannot contain fields of multiple types

9100

Internal system error

9101

The number of fields exceeds the limit

9102

The data source is not used

9103

Invalid external table join

9104

A maximum of two levels of association are supported

9105

The template to be queried does not exist

9501

The username is empty

9502

The application name is empty

9519

No template is specified

9600

Internal system error

9902

The plug-in field type is invalid

9999

This service is not available for this domain name

Data synchronization-related errors (10000 and later)

Error code

Description

10001

Failed to obtain the TDDL information because no TDDL group key is specified

10002

Failed to obtain the fields, or the table does not exist

10011

Failed to connect to agg

10012

Documents exist in the application

10013

The application does not use a custom schema

10110

The task has ended

10010

Some data sources have issues. The data that contains errors has been ignored

10014

Invalid data source type

10100

Failed to create the task because an unfinished task already exists

10101

No application ID is specified

10106

No application ID is specified

10107

No application ID is specified

10102

Invalid ACTION

10112

The number of documents exceeds the limit

10201

Failed to obtain the quota list

10202

Failed to update the quota

10301

Parameter error: The parameter is not specified or is in an invalid format

10302

Invalid time parameter

10303

No data source is configured

10304

The quota for the table is exceeded

10305

Invalid OSS parameter

10306

Invalid OSS bucket name

10307

Invalid OSS record type

10308

Logging is not enabled for the OSS bucket

10309

Unfinished tasks exist

10310

Failed to create the task because the application is not running

10311

Invalid time range

10312

The application description exceeds the length limit of 600 characters

10313

Invalid OSS content format

10314

The ACL network in the region where the OSS bucket resides is unreachable

10315

Invalid OSS bucket address information

10330

Invalid data source parameter

10350

Failed to connect to the ODPS service

10351

ODPS returned an error

10400

Invalid OSS prefix

10450

The field does not exist

4007

Failed to decode the JSON data