OpenSearch returns an error code and an error message when a request fails. Use this reference to identify the cause and take corrective action.
Common errors
The following errors occur most frequently. Each entry includes the cause and the steps to resolve it.
| Error code | Cause and resolution |
|---|---|
| 1000 | Request timed out. Retry the request. If the error persists, submit a ticket. |
| 2112 | The fields used in business sorting are not fully included in the index fields. Search results are not affected, but update the schema to eliminate this warning. |
| 3007 | API calls exceed the rate limit. Reduce the call frequency. |
| 4003 | Signature verification failed. To debug: use the sample document to verify you get the same signature. If the signature matches, confirm that common parameters (uppercase) are sorted alphabetically before request parameters (lowercase), and that encoding rules for spaces and special characters are followed. See the authorization documentation for details. |
| 4007 | Failed to parse the JSON body. The JSON contains double quotation marks (") or non-printable characters. Escape the characters or add a filter condition, then retry. |
| 4010 | Invalid timestamp. Set the TimeStamp parameter to the current time in the correct format. Timestamps have a validity period. |
| 5001 | User not found. This usually means the AccessKey pair or API endpoint is invalid. Verify both and retry. To find the API endpoint: log in to the OpenSearch console, go to Instance Management, click Manage in the Actions column, and check the API Endpoint section on the Instance Details page. |
| 5008 | AccessKey pair is disabled. Enable it on the AccessKey Pair page of the Resource Access Management (RAM) console. |
| 6013 | The sum of start and hit exceeds 5,000. For deep pagination, use the SCROLL operation with search_type=scan. See the API reference for details. |
| 6015 | Request dropped because logical computing unit (LCU) consumption per second exceeded the purchased quota. To increase the quota: in the OpenSearch console, go to Instance Management, find the application, and choose More > Scale Up in the Actions column. |
| 6127 | The request references attribute fields not configured in the application schema. Update the schema using offline changes, then retry. |
| 7500 | Internal server error. Submit a ticket. |
System errors (1000–1999)
| Error code | Description |
|---|---|
| 1000 | Internal error. |
| 1001 | Template not found. |
| 1003 | Invalid index type. |
| 1004 | Service unavailable. Try again later. |
Application-related errors (2000–2999)
| Error code | Description |
|---|---|
| 2001 | Application not found. |
| 2002 | Application already exists. |
| 2003 | Number of applications exceeds the limit. |
| 2004 | Invalid application name. The name can be up to 30 characters and can contain letters, digits, and underscores (_). |
| 2005 | Application name is required. |
| 2006 | New application name is required. |
| 2007 | Description exceeds the length limit. The description can be up to 300 characters. |
| 2008 | Invalid summary parameter. |
| 2009 | Failed to update the application status. |
| 2010 | Application is paused. |
| 2011 | Application is frozen. |
| 2012 | Application is not started. |
| 2013 | Failed to delete the application. The application does not exist. |
| 2014 | Failed to upload the file. |
| 2016 | Region is not specified. |
| 2017 | The application does not belong to the current region. |
| 2099 | This operation is not supported. |
| 2101 | Expression not found. |
| 2102 | Expression name already exists. |
| 2103 | Number of expressions in the application exceeds the limit. |
| 2104 | Invalid expression name. The name can be up to 30 characters and can contain letters, digits, and underscores (_). |
| 2105 | Expression name is required. |
| 2106 | New expression name is required. |
| 2107 | Expression description exceeds the length limit. The description can be up to 300 characters. |
| 2108 | Invalid expression description format. |
| 2109 | Invalid expression format. |
| 2110 | Expression exceeds the length limit. |
| 2111 | Expression ID is required. |
| 2112 | Invalid expression. |
| 2113 | Expression is required. |
| 2114 | Operation error. |
| 2201 | Rough sort expression name is required. |
| 2202 | Rough sort expression name already exists. |
| 2203 | Number of rough sort expressions exceeds the limit. |
| 2204 | Invalid rough sort expression name. The name can contain only letters, digits, and underscores (_). |
| 2205 | Rough sort expression name exceeds the length limit. |
| 2206 | Rough sort field must be numeric. |
| 2207 | Rough sort expression not found. |
| 2208 | Invalid rough sort expression. Make sure fields are specified in the expression. |
| 2209 | Invalid weight in the rough sort expression. The weight must be a non-zero number between -100,000 and 100,000. FLOAT values are precise to six decimal places. |
| 2210 | The name is reserved by the default rough sort expression. |
| 2211 | The timeliness() function parameter is not of the INT type. |
| 2112 | Invalid sort expression. |
| 2551 | The drop-down suggestion rule specified in the query does not exist. |
Document-related errors (3000–3999)
| Error code | Description |
|---|---|
| 3001 | Document is required. |
| 3002 | Document size exceeds the limit. |
| 3003 | Number of documents exceeds the limit. |
| 3004 | Failed to save the document. |
| 3005 | Invalid document format. |
| 3006 | Invalid document processing command. |
| 3007 | Too many requests in a short period. |
| 3008 | Document size is too large. |
| 3009 | Document ID is required. |
| 3011 | Pushing documents via API is not supported when an ApsaraDB RDS for MySQL or MySQL data source is configured. |
| 3012 | Resource not found. |
| 3013 | Document push rate exceeds the application limit. |
| 3014 | Document push rate exceeds the system limit. |
| 3015 | Number of documents pushed per request exceeds the limit. |
| 3016 | Total number of documents in the application exceeds the limit. |
Authorization-related errors (4000–4999)
| Error code | Description |
|---|---|
| 4001 | Authentication failed. |
| 4002 | Signature is required. |
| 4003 | Signature verification failed. |
| 4004 | SignatureNonce is required. |
| 4005 | SignatureNonce value is not unique. |
| 4006 | SignatureNonce verification failed. |
| 4007 | Failed to parse the JSON format. |
| 4008 | Username is required. Check that the domain name is correct. |
| 4009 | User ID is required. |
| 4010 | Invalid timestamp. |
| 4011 | This operation is not allowed for a demo account. |
| 4012 | The specified table does not exist. |
| 4013 | Invalid timestamp format. |
| 4014 | Timestamp parameter is required. |
| 4020 | RAM user authentication failed. |
User-related errors (5000–5999)
| Error code | Description |
|---|---|
| 5001 | User not found. |
| 5002 | Invalid username. |
| 5003 | User login is required. |
| 5004 | Account has overdue payments. |
| 5005 | OpenSearch is not activated. Activate the service on the Alibaba Cloud official website. |
| 5006 | Application is frozen due to overdue payments. |
| 5008 | AccessKey pair is disabled. |
| 5009 | User is deleted. |
| 5010 | AccessKey pair is disabled. |
| 5011 | Multiple users are registered with the same email address. |
| 5012 | CODE_USER_ALIYUN_USER_ID_INVALID. No error message is returned. |
| 5013 | CODE_USER_ALIYUN_BID_INVALID. No error message is returned. |
| 5014 | CODE_USER_CLIENT_ID_INVALID. No error message is returned. |
| 5015 | CODE_USER_ID_INVALID. No error message is returned. |
| 5100 | Not authorized to perform operations in this region. |
Search-related errors (6000–6999)
| Error code | Description |
|---|---|
| 6001 | Search query is required. |
| 6002 | Invalid keyword for key search. |
| 6003 | Invalid keyword for field search. |
| 6004 | Complex query is empty. |
| 6005 | Invalid field. |
| 6006 | Too many application names in the request. |
| 6007 | Total number of indexes per template in a multi-index query exceeds the limit. |
| 6008 | Failed to parse the request due to a syntax error. |
| 6009 | Query clause is too long. Use the filter clause instead — it supports up to 4 KB. Alternatively, use a combined index to group multiple TEXT or SHORT_TEXT fields into a single index. |
| 6010 | Invalid rerank size. |
| 6011 | Invalid SignatureNonce format. |
| 6013 | The sum of start and hit exceeds the limit. Use the SCROLL operation when start + hit > 5,000. |
| 6014 | Request dropped because the system is busy. |
| 6015 | Request dropped because LCU consumption exceeds the purchased quota. |
| 6016 | Number of query hits exceeds the limit. |
| 6017 | The scroll parameter requires search_type=scan. |
| 6018 | scroll is specified but search_type is not. |
| 6019 | Failed to parse the scroll_id parameter. |
| 6020 | Invalid value for the scroll parameter. |
| 6021 | The aggregate, sort, and distinct clauses are not supported in scroll requests. |
| 6022 | scroll_id has expired. |
| 6024 | Invalid value for the hit parameter in drop-down suggestions. |
| 6031 | Invalid value for the abtest parameter. |
| 6033 | Invalid value for the re_search parameter. |
| 6034 | Invalid value for the biz parameter. |
| 6100 | Search query is empty. |
| 6101 | The index field in the query does not exist. |
| 6102 | Invalid numeric range in the query clause. |
| 6103 | The expression in the filter clause does not return a BOOLEAN value. |
| 6104 | The expression in the sort clause returns a BOOLEAN value, which is not allowed. |
| 6105 | Duplicate expressions in the sort clause. |
| 6106 | Invalid query. |
| 6107 | A statistical function expression cannot return a boolean or string. |
| 6108 | The range in a statistical function is not in ascending order. |
| 6109 | Invalid return type of the range expression in a statistical function. |
| 6110 | Statistical function not found. |
| 6111 | Invalid statistical function. |
| 6112 | Invalid query clause. |
| 6113 | Invalid filter clause. |
| 6114 | Invalid aggregate clause. |
| 6115 | Invalid sort clause. |
| 6116 | Invalid distinct clause. |
| 6117 | Query contains unknown clauses. |
| 6118 | Syntax error. |
| 6119 | Invalid dist_count value in the distinct clause. The value must be an integer greater than 0. |
| 6120 | Invalid dist_times value in the distinct clause. The value must be an integer greater than 0. |
| 6121 | Invalid reserved value in the distinct clause. The value must be true or false. |
| 6122 | distinct_key is not specified in the distinct clause. |
| 6123 | Invalid grade value in the distinct clause. The value cannot be blank or non-numeric. |
| 6124 | Invalid distinct value in the distinct clause. The value must be in the range (0, 2]. |
| 6125 | Invalid max_item_count value in the distinct clause. The value must be an integer greater than 0. |
| 6126 | Invalid update_total_hit value in the distinct clause. The value must be true or false. |
| 6127 | The request references attribute fields not configured in the application schema. Update the schema using offline changes, then retry. |
| 6128 | Data types of operands on either side of the binary operator do not match. |
| 6129 | Both expressions on either side of a binary operator cannot be constants. |
| 6130 | Invalid value type in the binary logic expression. The value must be of the BOOLEAN type. |
| 6131 | STRING values in the binary expression are not supported. |
| 6132 | ARRAY values in the binary expression are not supported. |
| 6133 | Invalid value type for bit manipulation. |
| 6134 | Invalid data type returned by the constant expression. |
| 6135 | Invalid value type for the constant expression. LITERAL field values in the filter clause must be enclosed in double quotation marks ("). |
| 6140 | Aggregate clause syntax error. The SUM function is not supported for LITERAL field types. |
| 6300 | Constant expression type must be an integer or floating-point number. |
| 6301 | Operand for bitwise negation must be an integer. |
| 6302 | Operand for negation must be a number. |
| 6303 | Operand for logical NOT must be a number. |
| 6304 | Invalid operand type for the binary operation. |
| 6305 | Invalid binary operator. |
| 6306 | Invalid parameter type for the function. |
| 6307 | Function is not defined. |
| 6308 | Invalid number of parameters for the function. |
| 6309 | Invalid array function. |
| 6310 | No filterable field found. |
| 6311 | An array field is used as a single-value field. |
| 6312 | A single-value field is used as an array field. |
| 6313 | Invalid subscript for the array field. The value must be 0 or greater. |
| 6314 | Invalid field type. |
| 6315 | The specified index field does not exist. |
| 6316 | No index specified in the query. |
| 6317 | A formula is used more than once in the filter clause. Each formula can appear only once per filter clause. |
| 6318 | Failed to parse the formula syntax. |
| 6400 | Sort script not found. |
| 6450 | Error occurred while running the script. |
| 6500 | The search syntax references fields that do not exist. |
| 6501 | No index data in the online system. |
| 6502 | Invalid query syntax. |
| 6503 | The default operator OR is not supported. |
| 6504 | Accurate statistics are not supported. |
| 6505 | Invalid rank size. |
| 6506 | Too many terms returned after query analysis. |
| 6601 | An index field appears in more than one rule. Each index field can belong to only one rule. |
| 6602 | No search query specified (for example, default:"" is set). |
| 6603 | The index field in the query is not defined in any query analysis rule. |
| 6604 | Keyword is not enclosed in single quotation marks. Valid format: default:'xxx'. |
| 6605 | Keyword is enclosed in double quotation marks. Query analysis rules cannot be applied. |
| 6606 | The search query does not include the index to be analyzed. |
| 6607 | Invalid format for the disable parameter. |
| 6608 | The index field to disable does not exist. |
| 6609 | The feature list to disable does not exist. |
| 6610 | Query is empty after analysis. This may be because the original query is empty or contains only stop words. |
| 6611 | Index field is required in the query. |
| 6612 | term_weight makeup data failed. Intervention data did not take effect. |
| 6613 | Number of terms in the query clause exceeds the limit of 256. |
Data processing errors (7000–7999)
| Error code | Description |
|---|---|
| 7202 | Invalid command. Only UPDATE, ADD, and DELETE commands are supported. |
| 7301 | Primary key field not found. Data push failed because the document has no primary key value. |
| 7302 | Data type mismatch. Data push failed because the primary key value is invalid. |
| 7303 | Multiple primary key values in the document. Data push failed because a document can have only one primary key value. |
| 7304 | Primary key value is required. Data push failed because the primary key value is empty. |
| 7305 | Table does not exist in the current application. Data push failed because the table name is not recognized. |
| 7500 | Internal error. Submit a ticket. |
| 7503 | Data push failed. The field value returned by the JSON plug-in is not valid JSON. Check the value and retry. |
| 7504 | Data push failed. The key for the field value returned by the JSON plug-in does not exist. |
| 7505 | TairLDBExtractor plug-in configuration error. Failed to connect to Tair. Check that the configuration ID and namespace are valid. |
| 7510 | Data push failed. An error occurred during field processing by the KeyValueExtractor plug-in. |
| 7515 | Error occurred while executing the filter condition. |
| 7520 | Data push failed. A single document exceeds the 1 MB size limit. |
| 7523 | Data push failed. An error occurred during data processing by the StringConnector plug-in. |
| 7524 | Geo field value out of range. Longitude must be 180 or less; latitude must be 90 or less. |
| 7525 | Invalid format for the geo or range field. |
| 7601 | Error occurred while running the task. Submit a ticket. |
| 7602 | No data in the MaxCompute table. Make sure the table partitions contain data, then retry. |
| 7603 | Error occurred while configuring the ApsaraDB RDS for MySQL or PolarDB for MySQL data source. |
| 7605 | Taobao Distributed Data Layer (TDDL) configuration error. |
| 7607 | No permissions on the MaxCompute table. |
| 7608 | A source field does not exist in the MySQL data source. |
| 7620 | Query timeout on the data source. |
| 7803 | Data push failed. The document to update does not exist. |
| 7805 | Data push failed. An error occurred during data processing by the HTML plug-in. |
| 7807 | Field type and value mismatch. Type conversion failed; the field is set to its default value. |
| 73106 | Number of data push operations exceeds the limit. Increase the quota. |
Document-related internal errors (8000–8999)
| Error code | Description |
|---|---|
| 8001 | Failed to save the error message. |
| 8002 | Required parameters are missing. |
| 8003 | Application does not exist. |
| 8004 | One or more parameters are invalid. |
Template-related errors (9000–9999)
| Error code | Description |
|---|---|
| 9001 | Username is required. |
| 9002 | Application name is required. |
| 9003 | Invalid template name. The name can contain only letters, digits, and underscores (_). |
| 9004 | Template name exceeds 30 characters. |
| 9005 | Error occurred while querying template information. |
| 9006 | Template name already exists. |
| 9007 | Error occurred while inserting data into the template. |
| 9008 | Invalid data. |
| 9009 | Number of defined fields exceeds the system limit. |
| 9010 | Field name is reserved. |
| 9011 | Field name already exists. |
| 9012 | Invalid index name. Index names can be up to 30 characters, can contain letters, digits, and underscores (_), must start with a letter, and cannot be of the SWS_TEXT or TEXT type for multi-value fields. |
| 9013 | Arrays are not supported. |
| 9014 | Primary keys are not supported. |
| 9015 | Primary key is required. |
| 9016 | Primary key is not unique. |
| 9017 | Failed to update the information. |
| 9018 | Failed to delete the information. |
| 9019 | Number of search fields exceeds the limit. A maximum of four search fields can include multiple index fields. |
| 9020 | A STRING or TEXT index field is used in more than one single-field search field. |
| 9021 | Invalid index name. Index names can be up to 30 characters, can contain letters, digits, and underscores (_), and must start with a letter. |
| 9022 | This table has an existing association. |
| 9023 | The index name contains fields of different types, which is not allowed. |
| 9100 | Internal error. |
| 9101 | Number of fields exceeds the limit. |
| 9102 | This data source is not in use. |
| 9103 | Invalid secondary table connection. |
| 9104 | Number of association levels exceeds the limit. The maximum is two levels. |
| 9105 | The template to check does not exist. |
| 9501 | Username is required. |
| 9502 | Application name is required. |
| 9519 | No template specified. |
| 9600 | Internal error. |
| 9902 | Invalid field type for the plug-in. |
| 9999 | Service is not available for this domain name. |
Data synchronization errors (10000 and above)
| Error code | Description |
|---|---|
| 10001 | Failed to get TDDL information. The TDDL group key is not specified. |
| 10002 | Failed to get the field, or the table does not exist. |
| 10010 | Some data sources contain invalid data. Invalid data is skipped. |
| 10011 | Failed to connect to Aggregator. |
| 10012 | The application contains documents. |
| 10013 | The application schema is not a custom schema. |
| 10014 | Invalid data source type. |
| 10100 | Failed to create the task. Some tasks are already in progress. |
| 10101 | Application ID is required. |
| 10102 | Invalid action. |
| 10106 | Application ID is required. |
| 10107 | Application ID is required. |
| 10110 | Task is complete. |
| 10112 | Number of documents exceeds the limit. |
| 10201 | Failed to get the quota list. |
| 10202 | Failed to update the quota. |
| 10301 | One or more required parameters are missing or have an invalid format. |
| 10302 | Invalid time parameter. |
| 10303 | Data source not configured. |
| 10304 | Quota for this table exceeds the limit. |
| 10305 | Invalid Object Storage Service (OSS) parameter. |
| 10306 | Invalid OSS bucket name. |
| 10307 | Invalid OSS record type. |
| 10308 | Logging is disabled for the OSS bucket. |
| 10309 | Some tasks are already in progress. |
| 10310 | Application is not running. Tasks cannot be created. |
| 10311 | Invalid time range. |
| 10312 | Application description exceeds the length limit. The description can be up to 600 characters. |
| 10313 | Invalid OSS content format. |
| 10314 | Failed to access the access control list (ACL) in the region where the OSS bucket resides. |
| 10315 | Invalid endpoint for the OSS bucket. |
| 10330 | Invalid data source parameters. |
| 10350 | Failed to connect to the MaxCompute data source. |
| 10351 | Error in the MaxCompute data source. |
| 10400 | Invalid prefix for the OSS bucket name. |
| 10450 | Field does not exist. |
该文章对您有帮助吗？