Common error codes for video understanding
If an API request fails, the server returns an error message. This topic describes the error codes for the video understanding service.
If you have questions about API access, usage, or other issues with the visual AI capabilities of the Alibaba Cloud Visual Intelligence API, contact us through the DingTalk group (23109592).
Troubleshooting center
Use the Troubleshooting Center to efficiently diagnose problems with API calls.
Video understanding error codes
Status code | Error code | Description |
403 | AuthFailed | Authorization failed. Check the RAM permission configuration. |
400 | ClientError.IllegalArgument | Check the parameters. For example, check if the database represented by a parameter value exists. |
400 | EntityNotExist.Role | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access permissions using RAM policies. |
400 | IllegalUrlParameter | The URL is invalid. Check if the URL can be opened. For image URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
500 | InternalError | An internal server error occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Algo | An internal algorithm processing error occurred. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Busy | The algorithm service is busy. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Model | A model loading error occurred. Retry later. If this affects your business, contact us through the DingTalk group (23109592). |
500 | InternalError.Timeout | The algorithm service timed out during internal processing. Retry later. If this affects your business, contact us through the DingTalk group (23109592). |
400 | InvalidAccessKeyId.Inactive | The AccessKey ID is invalid. Check if the AccessKey ID is disabled, or if the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAccessKeyId.NotFound | The AccessKey ID was not found. Check if the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAccessKeySecret | The AccessKey ID or AccessKey secret is incorrect. Check if the AccessKey ID and AccessKey secret are correct. |
400 | InvalidAction.NotFound | The capability was not found. Check if the category and capability match. Also, check if the endpoint and capability match. For more information, see Endpoints. Choose a programming language and modify the sample code to connect. For more information, see SDK overview. |
400 | InvalidApi.ForbiddenInvoke | The call is restricted. Check if the capability you are calling is restricted. Restricted capabilities must be requested in the console. You can call them only after approval or manual activation. If this is not the case, check if your account has an overdue payment. |
400 | InvalidApi.NotPurchase | The service is not activated. Activate the service first. |
400 | InvalidApi.OutOfService | The product is not activated. Activate the product. |
400 | InvalidFile.Category | The file content category does not meet the requirements. |
400 | InvalidFile.Content | The data is empty or cannot be processed. |
400 | InvalidFile.Decode | The file cannot be decoded. |
400 | InvalidFile.Download | The file cannot be downloaded. Check your on-premises network and if the link is accessible. For file URLs that are not for OSS in the China (Shanghai) region, see Handle file URLs. |
400 | InvalidFile.Region | The file URL does not belong to the specified region. |
400 | InvalidFile.Resolution | The file resolution is invalid. |
400 | InvalidFile.Type | The file type is invalid. Check the file type and use a type that is supported by the algorithm. For more information, see the API reference for the algorithm. The Alibaba Cloud Visual Intelligence API determines the file type by reading the file, not from its extension. Relying only on the file extension is invalid. For more information about file type detection and handling, see File type detection and handling. |
400 | InvalidFile.Unsafe | The file link is unsafe. |
400 | InvalidFile.URL | Invalid file URL. |
400 | InvalidImage.Content | Check the image content against the algorithm document. Replace the image with one that meets the algorithm requirements. |
400 | InvalidImage.Decode | Check if the image can be opened correctly. |
400 | InvalidImage.Download | If an image fails to download, check the local network connection. Then, make sure the link works and the OSS link has not expired. For image links from OSS regions other than Shanghai, see Process file URLs. URLs do not support spaces or Chinese characters. If a URL contains these characters, encode it using URLEncode before you pass it. |
404 | InvalidImage.NotFoundFace | No face was found in the image. Check if the image contains a face or if the face is too small. |
400 | InvalidImage.REGION | The image URL has an incorrect region. It is not a URL for an OSS file in the Shanghai region. For more information, see Process file URLs. |
400 | InvalidImage.Resolution | The file resolution exceeds the limit. Check the file resolution and content. Modify the resolution and retry. |
400 | InvalidImage.Timeout | The image download timed out. Check that the link is accessible and that your local network is connected. |
400 | InvalidImage.Type | Incorrect image type. See the algorithm API documentation for supported image types. |
400 | InvalidImage.URL | The image link is invalid. Check if the link is accessible. For image links not from OSS in the Shanghai region, see File URL Processing. For OSS links in the Shanghai region, use a standard OSS domain name. Attaching accelerated domain names and custom domain names is not supported. |
400 | InvalidParameter | The request parameter is invalid. |
400 | InvalidParameter.BadRequest | The request parameter is missing or invalid. |
400 | InvalidParameter.Format | Incorrect input parameter format. |
400 | InvalidParameter.NotFound | Parameter fault. Check the parameter value against the algorithm API documentation and the error message. Ensure that the value does not have leading or trailing spaces or other special characters. |
400 | InvalidParameter.TooLarge | Parameter error: the file size exceeds the limit. Refer to the algorithm API documentation to adjust the file size. |
400 | InvalidRamRole | If you do not have RAM permissions, contact the Alibaba Cloud account to grant you the AliyunVIAPIFullAccess permission. For instructions, see Control access using RAM policies. |
400 | InvalidResult | Invalid parameter. Refer to the documentation to check the parameter values and the file content. Ensure that the image is not incomplete or too blurry. |
400 | InvalidSide | Specified parameter Side is not valid. Refer to the documentation for valid values. |
400 | InvalidTimeStamp.Expired | The timestamp has expired. Update the timestamp. |
400 | MissingAccessKeyId | The AccessKeyID was not entered. Check if the AccessKeyID and AccessKeySecret are correct. |
400 | MissingParameter | Missing input parameter. |
400 | ParameterError | Parameter error. Check the parameter value. |
503 | ServiceUnavailable | The service is unavailable. If the server returned a RequestId, contact us in the DingTalk group (23109592). |
400 | SignatureDoesNotMatch | The signature is incorrect. Recalculate the signature. For more information, see Request Signature. |
400 | SignatureNonceUsed | The signature has already been used. Recalculate the signature. For more information, see Request signature. |
400 | Throttling | Throttling was triggered. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through the DingTalk group (23109592). Note When throttling is triggered, both Throttling and Throttling.User may occur. Consider both when handling the error. |
400 | Throttling.User | The traffic for this period has exceeded the limit. For paid APIs, purchase a higher QPS. For free APIs with special requirements, contact us through the DingTalk group (23109592). Note When throttling is triggered, both Throttling and Throttling.User may occur. Consider both when handling the error. |
408 | Timeout | The request timed out. |
400 | Unauthorized | You do not have RAM permissions. Contact the root account to grant you the AliyunVIAPIFullAccess permission. For more information, see Control access permissions using RAM policies. |
Common error codes
For common API error codes, see the API Error Center.
Suggestions
If a service request returns an error code, refer to the error description to identify the cause and resolve the issue. The following suggestions can help you handle common types of errors.
URL-related error codes
These error codes usually indicate that the file URL does not meet the requirements. For example, the URL is unsafe or invalid. For more information, see Handle file URLs.
Image loading error codes
These errors are also related to image URLs and can be caused by issues such as download failures or an incorrect region. The recommended region is China (Shanghai). If you generate a URL using Object Storage Service (OSS), the bucket that you create in OSS must be in the China (Shanghai) region. For more information, see Handle file URLs.
Parameter-related error codes
These error codes usually indicate that the input parameters do not meet the requirements. For example, a parameter is missing or has an incorrect type. Check the request parameters table in the API document to confirm that your input parameters are correct.
System service error codes
If this type of error occurs, retry the service request. If the problem persists, report the issue in the DingTalk group (23109592).