Error Codes
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Code |
Message |
Description |
Solution |
---|---|---|---|---|
400 |
RF.10011001 |
Missing required parameter(s). |
Some required parameters are missing. |
Contact technical support. |
400 |
RF.10011002 |
Unrecognized parameter(s). |
Unrecognized parameters are provided. |
Contact technical support. |
400 |
RF.10011003 |
Both template_uri and template_body are given, you should only give exactly one parameter from template_uri and template_body. |
Either template_body or template_uri must be specified but they both cannot be specified together. |
Contact technical support. |
400 |
RF.10011005 |
The length of parameter is longer than upper limit. |
The length of the parameter exceeds the upper limit. |
Contact technical support. |
400 |
RF.10011006 |
The length of parameter is shorter than lower limit. |
The length of the parameter is shorter than the minimum length. |
Contact technical support. |
400 |
RF.10011008 |
Parameter contains invalid letter. Should only contains English characters, number or hyphen. |
The parameter contains invalid characters. Only letters, digits, and hyphens (-) are allowed. |
Contact technical support. |
400 |
RF.10011009 |
Parameter contains invalid letter. Should only contains lower case English characters, number or hyphen. |
The parameter contains invalid characters. Only lowercase letters, digits, and hyphens (-) are allowed. |
Contact technical support. |
400 |
RF.10011028 |
Composite Validation Error. |
Compound verification error. |
Contact technical support. |
400 |
RF.10011029 |
Parameter contains invalid letter. Should only contains English characters or number. |
The parameter contains invalid characters. Only letters and digits are allowed. |
Contact technical support. |
400 |
RF.10011031 |
Parameter contains invalid letter. Should only contains English characters, number, hyphen or underscore. |
The parameter contains invalid characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. |
Contact technical support. |
400 |
RF.10011032 |
Can not find request body. |
The request body is not transferred. |
Contact technical support. |
400 |
RF.10011036 |
The value of parameter is not a valid instance of integer. |
The parameter value is not of the valid integer type. |
Contact technical support. |
400 |
RF.10011039 |
VarKey contains invalid letter. VarKey should Starts with an English letter and only contains English characters, number, hyphen or underscore. |
var_key contains invalid characters. It must start with a letter and contains only letters, digits, hyphens (-), and underscores (_). |
Contact technical support. |
400 |
RF.10011049 |
Invalid vars uri. |
Invalid parameter link. |
Contact technical support. |
400 |
RF.10011050 |
Invalid vars uri content. |
File content from an invalid parameter link. |
Contact technical support. |
400 |
RF.10011051 |
Invalid vars body. |
Invalid vars body. |
Contact technical support. |
400 |
RF.10011052 |
Var value is empty. |
Empty variable value. |
Contact technical support. |
400 |
RF.10011055 |
Invalid json array. |
Invalid JSON array. |
Contact technical support. |
400 |
RF.10011056 |
Both template_uri and template_body are absence, you should give exactly one parameter from template_uri and template_body. |
Both template_uri and template_body are missing. Either of them must be specified but they both cannot be specified together. |
Contact technical support. |
400 |
RF.10011057 |
Project ID should only contains lower case hexadecimal characters. |
The project ID must contain only lowercase hexadecimal letters. |
Contact technical support. |
400 |
RF.10011065 |
Found duplicate values in attribute provider_name. |
Duplicate values are found in the provider_name attribute. |
Contact technical support. |
400 |
RF.10011073 |
Invalid template body. |
Invalid template body. |
Contact technical support. |
400 |
RF.10011074 |
Invalid template. |
Invalid template. |
Contact technical support. |
400 |
RF.10011075 |
File type is not matched with file content. |
The file type does not match the file content. |
Contact technical support. |
400 |
RF.10011084 |
No parameters in the request need to be modified. |
No parameters in the request need modification. |
Contact technical support. |
403 |
RF.10012538 |
The total count of stacks has exceeded the maximum limit. |
The number of stacks exceeds the upper limit. |
Contact technical support. |
403 |
RF.10012540 |
Too many stacks are being created in parallel, please take a rest and try again later. |
Too many stacks are created concurrently. Try again later. |
Contact technical support. |
403 |
RF.10012541 |
Too many execution plans are being created in parallel, please take a rest and try again later. |
Too many execution plans are created concurrently. Try again later. |
Contact technical support. |
403 |
RF.10012544 |
Stack cannot be deleted due to invalid stack status. |
The stack cannot be deleted due to its invalid status. |
Contact technical support. |
404 |
RF.10013001 |
Stack is not exist. |
The stack does not exist. |
Contact technical support. |
404 |
RF.10013002 |
Execution plan is not exist. |
The execution plan does not exist. |
Contact technical support. |
409 |
RF.10013501 |
Conflict execution plan name. Execution plan with name already exist. |
An execution plan with the same name already exists. |
Contact technical support. |
409 |
RF.10013502 |
Conflict stack name. Stack with name already exist. |
A stack with the same name already exists. |
Contact technical support. |
429 |
RF.10014001 |
Too many requests. Please try again in a few minutes. |
Too many requests. Try again later. |
Contact technical support. |
500 |
RF.10010001 |
Internal Server Error. |
Internal server error. |
Contact technical support. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot