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 make corrections promptly so that requests can be processed as expected.
Common errors and solutions
Error code | Solution |
1000 | This error is typically caused by a timeout. Retry the request and check whether the error persists. If the error persists, submit a ticket. Our on-duty staff will troubleshoot the issue as soon as possible. |
2112 | The field specified in text features such as text_relevance(field) and fieldterm_proximity(field) in a sort expression must be one of the source fields included in the queried index. Otherwise, an error is reported, but the search results are not affected. |
3007 | The system limits the frequency of API pushes. Control the request frequency and try again. |
4003 | First, follow the example in the documentation to check whether your signature result matches the expected result, which helps determine whether the issue lies in the signature algorithm. If it does not, check that after the parameters are sorted in lexicographic order, the common parameters (uppercase letters) come first and the request parameters (lowercase letters) come after. In addition, encoding rules apply to items such as spaces. For more information, see the authorization documentation. |
4007 | In most cases, JSON parsing fails because the JSON field content contains double quotation marks or invisible characters. Escape or filter out these characters and try again. |
4010 | The TimeStamp parameter has an expiration time. Use the current time in the required format for the calculation. |
5001 | No corresponding user is found. This is typically caused by incorrect AccessKey information or an incorrect regional endpoint. The API endpoint must be the one shown in Application Management > Basic Information > API Endpoint. Check and correct the information, and then try again. |
5008 | The service verifies user identity 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 sum of start and hit cannot exceed 5000. Otherwise, an error is reported and no results are returned. If you need to retrieve more than 5000 results, refer to the SCROLL operation in the API documentation to see whether it meets your requirements. |
6015 | The request is discarded because the computing resources (LCUs) exceed the purchased quota. Log on to the console, and on the application list page, click "Scale/Change Specifications" to scale out. |
6127 | Except for the query clause, all fields used in other clauses must be configured as attribute fields. Modify the application schema and try again. 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, the 26 English 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 remarks 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 | The 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 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, the 26 English 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 remarks cannot exceed 300 characters. |
2108 | The format of the expression remarks 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 | The operation is invalid. |
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, the 26 English letters, and underscores (_). |
2205 | The length of the rough sort configuration name exceeds the limit. |
2206 | The rough sort field 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 decimal places. |
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 drop-down suggestion rule specified in the query 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 endpoint 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 | RAM user authentication failed. |
User-related errors (5000-5999)
Error code | Description |
5001 | The user does not exist. |
5002 | The username is incorrect. |
5003 | User logon is required. |
5008 | The user has not enabled the AccessKey pair. |
5100 | The user does not have permissions to perform operations 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 the AccessKey pair. |
5009 | The user has been deleted. |
5010 | The AccessKey pair has been disabled. |
5011 | Multiple users are obtained based on 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 permissions to perform operations in this region. |
Search-related errors (6000-6999)
Error code | Description |
6001 | The query is empty. |
2022 | App version is unavailable. The query is performed on a version whose index rebuilding is not complete. That is, the status of the index rebuilding version is not "Normal". You can view the status on the application details page. |
6002 | The search key is not supported. |
6003 | The search 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 syntax of the request string is invalid, and parsing failed. |
6009 | The query clause is too long. |
6010 | The rerank size is invalid. |
6011 | The SignatureNonce format is invalid. |
6013 | The sum of start and 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. Valid values: [0,500]. |
6017 | Currently, scroll supports only the search_type value scan. That is, if you set the scroll parameter, you must set the search_type parameter to 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 search term is empty. |
6101 | The queried index field 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 duplicate 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 the aggregation must be in ascending order. |
6109 | The return value type of the range expression in the 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 entries in the Distinct clause is invalid. The number must be in the range of (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 try again. You can configure attribute fields by using offline changes. |
6128 | The result types of the expressions on both sides of a binary operator in the expression do not match. |
6129 | The expressions on both sides of a binary operator in the expression 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. |
6140 | Aggregate clause syntax error, SUM is not supported for fields of the LITERAL type. |
6300 | The type of the constant expression must be an integer or a floating-point number. |
6301 | The operand of a bitwise NOT operation must be an integer. |
6302 | The operand of a negation operation must be a numeric value. |
6303 | The operand of a logical NOT operation 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 subscript 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 being executed. |
6500 | The search syntax contains a field that does not exist. |
6501 | The online system has no index data. |
6502 | The user query syntax is invalid. |
6503 | The default operator OR is not supported. |
6504 | Exact aggregation is not supported. |
6505 | The rank size is invalid. |
6506 | Too many terms are generated after the query is tokenized. |
6601 | An index field can be included in only one rule. |
6602 | No search term is specified, 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 an index that requires 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 it 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. |
6136 | Unsupported Expression type. An invalid expression is used in the clause. For example, sort=-2 contains a constant. |
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 that corresponds to the JSON plug-in is not JSON. The content of the JSON plug-in field is not in the JSON format, and the push failed. Check the content and try again. |
7504 | The key that corresponds 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 the configId or namespace is valid. |
7510 | An error occurred when the keyvalue plug-in (KeyValueExtractor) processed the field, and the push failed. |
7515 | An error occurred when the filter condition was executed. |
7523 | An error occurred in the StringConnector plug-in, and the push failed. |
7524 | The geo field content is out of range. The range field content exceeds the longitude and latitude range (lon>180; lat>90). |
7525 | The geo field format is invalid. The range field content format is incorrect. |
7601 | An error occurred when 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. Make sure that the odps partition is generated as expected and try again. |
7607 | No permissions on odps. |
7603 | The MySQL data source (RDS/POLARDB) configuration is invalid. |
7605 | TDDL configuration error |
7608 | A source field is 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 in the HTML plug-in |
7807 | The field type does not match the field content and the content failed to be converted to the destination type. A default value will be used for the field |
73106 | The push quota is exceeded. Scale out the application |
Internal notifications for document errors (8000-8999)
Error code | Description |
8001 | Failed to save the error information |
8002 | A required parameter is 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 4 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 of this type exceeds the limit |
9102 | The data source is not used |
9103 | Invalid join with an external table |
9104 | A maximum of 2 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 field type of the plug-in is incorrect |
9999 | This service is not provided for this domain name |
Data synchronization-related errors (10000-)
Error code | Description |
10001 | The specified TDDL group key does not exist. Failed to obtain the TDDL information |
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 | Incorrect 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 provided or is in an invalid format |
10302 | Invalid time parameter |
10303 | The data source is not configured |
10304 | The quota of 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 | An unfinished task exists |
10310 | The task cannot be created because the application is not running |
10311 | Invalid time range |
10312 | The application description exceeds the length limit. The description can contain a maximum of 600 characters |
10313 | Invalid OSS content format |
10314 | The ACL network in the region where the OSS bucket resides is inaccessible |
10315 | Invalid OSS bucket address |
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 |