This topic describes the error codes of Alibaba Cloud Model Studio and causes of the errors.
Status codes
An API call to Alibaba Cloud Model Studio returns a status code that indicates the result of the call. The following table describes the general status codes that are defined by Alibaba Cloud Model Studio. In addition to the general status codes, models may add custom status codes and messages. You can identify a call result based on the code and status parameters.
HTTP status code | Code | Message (Specific messages may vary in different scenarios) | Description |
400 | InvalidParameter | Required parameter(s) missing or invalid, please check the request parameters. | Request parameters are invalid. |
400 | DataInspectionFailed | Input or output data may contain inappropriate content. | The input or output data may contain inappropriate content and is blocked during content moderation. |
400 | BadRequest.EmptyInput | Required input parameter missing from request. | The input cannot be empty. |
400 | BadRequest.EmptyParameters | Required parameter "parameters" missing from request. | Request parameters cannot be empty. |
400 | BadRequest.EmptyModel | Required parameter "model" missing from request. | The request model cannot be empty. |
400 | InvalidURL | Invalid URL provided in your request. | The request URL is incorrect. |
400 | Arrearage | Access denied, plesase make sure your account is in good standing. | Access denied because of overdue payments. |
400 | UnsupportedOperation | The operation is unsupported on the referee object. | The referee object does not support this operation. This message may vary based on the actual scenario. |
400 | FlowNotPublished | Flow has not published yet, please publish flow and try again. | The flow is not published. Publish the flow and try again. |
400 | InvalidSchema | Database schema is invalid for text2sql. | Enter the schema of your database. |
400 | InvalidSchemaFormat | Database schema format is invalid for text2sql. | The schema format of the input data table is invalid. |
400 | FaqRuleBlocked | Input or output data is blocked by faq rule. | The input or output is blocked by FQA rules. |
400 | CustomRoleBlocked | Input or output data may contain inappropriate content with custom rule. | The input or output is blocked by custom rules. |
401 | InvalidApiKey | Invalid API-key provided. | The input API key is invalid. |
403 | AccessDenied | Access denied. | You are not authorized to access this API. For example, you are not in the invitational preview. |
403 | Workspace.AccessDenied | Workspace access denied. | You are not authorized to access the applications or models in this workspace. Check whether you specified the valid workspace ID. If you want to call a model, see Call a model in a sub-workspace. |
403 | Model.AccessDenied | Model access denied. | The Resource Access Management (RAM) user is not authorized to access models in this workspace. Perform the following steps:
For more information, see the Prerequisites section of the Call a model in a sub-workspace topic. |
403 | AccessDenied.Unpurchased | Access to model denied. Please make sure you are eligible for using the model. | The model is not activated. |
404 | WorkSpaceNotFound | WorkSpace can not be found. | The workspace that you specified does not exist. |
404 | ModelNotFound | Model can not be found. | The model that you specified does not exist. |
408 | RequestTimeOut | Request timed out, please try again later. | The request timed out. |
413 | BadRequest.TooLarge | Payload Too Large | The gateway at the access layer returns an error that the request body is too large. If the error is returned by the Microservice Engine (MSE) gateway, no code is returned and the message cannot be customized. If the error is returned by the RESTful gateway, a code is returned. |
415 | BadRequest.InputDownloadFailed | Failed to download the input file: xxx | Failed to download the input file, which may be due to download timeout, download failure, or file size exceeding the limit. The message may include additional details. |
415 | BadRequest.UnsupportedFileFormat | Input file format is not supported. | The format of the input file is not supported. |
429 | Throttling | Requests throttling triggered. | The API call triggers throttling. |
429 | Throttling.RateQuota | Requests rate limit exceeded, please try again later. | The frequency of calls triggers throttling, such as the number of requests per second. |
429 | Throttling.AllocationQuota | Allocated quota exceeded, please increase your quota limit. | The number of calls triggers throttling, such as the number of tokens generated per minute. |
429 | Throttling.AllocationQuota | Free allocated quota exceeded. | Free quota is exhausted and billable access of the model is not enabled. |
429 | PrepaidBillOverdue | The prepaid bill is overdue. | Subscription of this workspace is overdue. |
429 | PostpaidBillOverdue | The postpaid bill is overdue. | The model inference service is overdue. |
429 | CommodityNotPurchased | Commodity has not purchased yet. | The service is not activated in this workspace. |
500 | InternalError | An internal error has occured, please try again later or contact service support. | An internal error occurred. |
500 | InternalError.Algo | An internal error has occured during execution, please try again later or contact service support. | An internal algorithm error occurred. |
500 | SystemError | An system error has occured, please try again later. | A system error occurred. |
500 | InternalError.Timeout | An internal timeout error has occured during execution, please try again later or contact service support. | An asynchronous task timed out, 3 hours after it was submitted from the gateway to the algorithm service layer. |
500 | RewriteFailed | Failed to rewrite content for prompt. | Prompt rewriting failed. |
500 | RetrivalFailed | Failed to retrieve data from documents. | Document retrieval failed. |
500 | AppProcessFailed | Failed to proceed application request. | Application flow processing failed. |
500 | ModelServiceFailed | Failed to request model service. | Model service call failed. |
500 | InvokePluginFailed | Failed to invoke plugin. | Plug-in call failed. |
503 | ModelUnavailable | Model is unavailable, please try again later. | The model is temporarily unavailable for service. |
Response parameters
In addition to an HTTP status code, a message that contains the details of the error is returned. Sample response:
{
"request_id": "54dc32fd-968b-4aed-b6a8-ae63d6fda4d5",
"code": "InvalidApiKey",
"message": "The API key in your request is invalid."
}Response parameters
Parameter | Type | Description |
HTTP status code | integer | The status code 200 indicates that the request is successful. Other status codes indicate that the request failed. If the request failed, the corresponding error code and error message are returned in the code and message parameters. |
request_id | string | The request ID. You can identify a call based on the request_id parameter during troubleshooting. |
code | string | The error code returned in case of failure. For more information, see the Code column of the Status code table of this topic. |
message | string | The message returned in case of failure. For more information, see the Code column of the Status code table of this topic. Take note that the message may vary based on the actual scenario and may contain more specific information that is different from the preceding table. |