Error Codes
Status Code |
Error Code |
Error Message |
Description |
---|---|---|---|
400 |
FSS.0400 |
Invalid parameter. |
Invalid request parameters. |
401 |
FSS.0401 |
Unauthorized access. |
Access denied. |
403 |
FSS.0403 |
Forbidden |
Unauthorized operation. |
404 |
FSS.0404 |
The specified resource was not found. |
The resource cannot be found. |
406 |
FSS.0406 |
Not acceptable. |
Incorrect request format. For example, the request body may not be in the required JSON format. |
408 |
FSS.0408 |
Request timeout. |
Request timed out. |
409 |
FSS.0409 |
The specified resource already exists. |
The resource already exists. |
410 |
FSS.0410 |
The specified resource does not exist. |
The specified resource does not exist. |
413 |
FSS.0413 |
The request body is too large. |
The request body exceeds the maximum allowed limit. |
424 |
FSS.0424 |
Invalid dependency. |
Invalid dependency. |
426 |
FSS.0426 |
An upgrade is required. |
Unsupported operation. Perform an upgrade. |
428 |
FSS.0428 |
The preconditions have not been met. |
The prerequisite has not been met. For example, you must delete related resources before deleting a resource. |
429 |
FSS.0429 |
Too many requests. |
Too many concurrent requests. Please try again later. |
500 |
FSS.0500 |
Internal server error. |
The service is temporarily abnormal due to an internal invocation error. Please try again later. |
502 |
FSS.0502 |
Bad gateway. |
Gateway error. |
503 |
FSS.0503 |
Service unavailable. |
Service unavailable. |
504 |
FSS.0504 |
Gateway timeout. |
Gateway timed out. |
400 |
FSS.1001 |
Invalid query parameter. |
Invalid query parameter. |
400 |
FSS.1002 |
Invalid function name. |
Invalid function name. |
400 |
FSS.1003 |
Invalid function handler. |
Invalid handler. |
400 |
FSS.1004 |
Invalid Package (function app). |
Invalid function package. |
400 |
FSS.1005 |
Invalid runtime. |
Invalid runtime. |
400 |
FSS.1006 |
Invalid function code entry mode. |
Invalid code type. |
400 |
FSS.1007 |
Invalid function memory. |
Invalid memory. |
400 |
FSS.1008 |
Invalid function timeout. |
Invalid timeout. |
400 |
FSS.1009 |
Invalid function UserData. |
Invalid environment variables. |
400 |
FSS.1010 |
Invalid URL. |
Invalid URL. |
400 |
FSS.1011 |
Invalid function code. |
Invalid function code. |
400 |
FSS.1012 |
The function code must be configured. |
The function code cannot be left blank. |
400 |
FSS.1013 |
Invalid file type. |
Invalid file type. |
400 |
FSS.1014 |
Invalid function alias. |
Invalid alias. |
400 |
FSS.1015 |
Invalid function version. |
Invalid version. |
400 |
FSS.1016 |
The function cannot be published because no changes have been made since last publication. |
The function code cannot be published because it has not been changed since last publication. |
400 |
FSS.1017 |
The number of items in the UserData field exceeds the maximum allowed limit (20). |
The number of environment variables exceeds 20. |
400 |
FSS.1018 |
The total size of the UserData field exceeds the maximum allowed limit (2 KB). |
The total size of environment variables exceeds 2 KB. |
400 |
FSS.1019 |
The description exceeds the maximum allowed limit. |
The maximum length is 512 characters. |
400 |
FSS.1022 |
Only one YAML file is allowed. |
Only one YAML file is allowed. |
400 |
FSS.1023 |
The imported file is too large. |
The imported file exceeds the maximum allowed limit. |
400 |
FSS.1024 |
Invalid dependency. |
Invalid dependency. |
400 |
FSS.1025 |
Invalid YAML file. |
Invalid YAML file. |
400 |
FSS.1026 |
Invalid Concurrency. |
Invalid concurrency policy. |
400 |
FSS.1027 |
Invalid packageName (app name). |
Invalid package or app name. |
400 |
FSS.1028 |
The app cannot be deleted because it contains functions. |
The app cannot be deleted because it contains functions. |
400 |
FSS.1029 |
The default app cannot be deleted. |
The default app cannot be deleted. |
400 |
FSS.1031 |
The dependency already exists. |
The dependency already exists. |
400 |
FSS.1032 |
Invalid dependency type. |
Invalid dependency type. Currently, only local ZIP packages or packages from OBS can be uploaded. |
412 |
FSS.1033 |
The dependency is currently in use. |
Failed to delete the dependency because it is in use. |
400 |
FSS.1034 |
Invalid image URL. |
Invalid image URL. |
400 |
FSS.1035 |
The image does not exist. |
The image does not exist. |
400 |
FSS.1036 |
The VPC does not exist. |
The VPC does not exist. |
400 |
FSS.1037 |
No subnet matches the specified ID. |
No matched subnets found. |
400 |
FSS.1038 |
The file system configuration already exists in the function. |
The file system configuration already exists in the function. |
400 |
FSS.1039 |
The mounting path is invalid. |
Invalid mounting path. |
403 |
FSS.1040 |
The selected Xrole does not have permissions to mount the resources. |
The selected agency does not have permissions to mount the resources. |
403 |
FSS.1041 |
The number of functions exceeds the maximum allowed limit. |
The number of functions exceeds 400. |
403 |
FSS.1042 |
The total code size of functions exceeds the maximum allowed limit. |
The total size of functions exceeds 20 GB. |
403 |
FSS.1043 |
The number of aliases exceeds the maximum allowed limit. |
The number of aliases exceeds the maximum allowed limit. |
403 |
FSS.1044 |
The number of apps exceeds the maximum allowed limit (400). |
The number of apps exceeds 400. |
403 |
FSS.1045 |
The number of dependencies exceeds the maximum allowed limit. |
The number of dependencies exceeds the maximum allowed limit. |
403 |
FSS.1046 |
The dependency is inaccessible. |
The dependency is unavailable. |
403 |
FSS.1047 |
The number of bound VPCs exceeds the maximum limit allowed for a tenant. |
The number of bound VPCs exceeds the maximum limit allowed for a tenant. |
403 |
FSS.1048 |
The number of bound VPCs exceeds the maximum limit allowed for a project. |
The number of bound VPCs exceeds the maximum limit allowed for a project. |
403 |
FSS.1049 |
The number of file systems mounted to the function exceeds the maximum allowed limit (5). |
The number of file systems mounted to the function exceeds 5. |
404 |
FSS.1050 |
The mounted resource cannot be found. |
The mounted resource cannot be found. |
404 |
FSS.1051 |
The function does not exist. |
The function cannot be found. |
404 |
FSS.1052 |
The version does not exist. |
The version cannot be found. |
404 |
FSS.1053 |
The alias does not exist. |
The alias cannot be found. |
404 |
FSS.1054 |
The function app does not exist in OBS. |
The specified code package cannot be found in OBS. |
404 |
FSS.1055 |
The app does not exist. |
The specified function app cannot be found in OBS. |
404 |
FSS.1056 |
The dependency does not exist. |
The dependency does not exist. |
404 |
FSS.1057 |
The function name does not exist in the YAML file. |
The function name does not exist in the YAML file. |
400 |
FSS.1058 |
The app name and function name cannot be the same in the YAML file. |
The combination of the app name and function name cannot be the same in the YAML file. |
404 |
FSS.1059 |
The function template does not exist. |
The function template does not exist. |
404 |
FSS.1060 |
The event template cannot be found. |
The event template does not exist. |
409 |
FSS.1061 |
The function already exists. |
The function already exists. |
409 |
FSS.1062 |
The version already exists. |
The version already exists. |
409 |
FSS.1063 |
The alias already exists. |
The alias already exists. |
409 |
FSS.1064 |
The app already exists. |
The app already exists. |
409 |
FSS.1065 |
The dependency already exists. |
The dependency already exists. |
409 |
FSS.1066 |
The version is already in use by another alias. |
The version is already in use by another alias. |
409 |
FSS.1067 |
The function template already exists. |
The function template already exists. |
403 |
FSS.1068 |
The number of events configured for the function exceeds the maximum allowed limit. |
The number of events configured for the function exceeds the maximum allowed limit. |
403 |
FSS.1069 |
The size of EventData exceeds 4 KB. |
The event size exceeds 4 KB. |
404 |
FSS.1070 |
The event cannot be found. |
The event cannot be found. |
413 |
FSS.1071 |
The size of the code package to be uploaded exceeds the maximum allowed limit (50 MB). |
The size of the code package to be uploaded exceeds 50 MB. |
413 |
FSS.1072 |
The size of the inline code exceeds the maximum allowed limit (10 KB). |
The code exceeds 10 KB. |
403 |
FSS.1073 |
The function event already exists. |
The function event already exists. |
400 |
FSS.1074 |
The event field is invalid. |
Invalid event field. |
400 |
FSS.1075 |
The user ID and user group ID must be an integer from –1 to 65,534, excluding 0, 1000, and 1002. |
The user ID and user group ID must be an integer from –1 to 65,534, excluding 0, 1000, and 1002. |
412 |
FSS.1090 |
The subnet is not in the ACTIVE state. |
The subnet is not in the ACTIVE state. |
400 |
FSS.1091 |
The additional version is invalid. |
Invalid additional version. |
400 |
FSS.1092 |
The weight of the additional version is invalid. |
The weight of the additional version is invalid. |
400 |
FSS.1093 |
The major version and the additional version cannot be the same. |
The major version and the additional version cannot be the same. |
403 |
FSS.1094 |
The version cannot be deleted because it has been used as the additional version of an alias. |
The version cannot be deleted because it has been used as the additional version of an alias. |
412 |
FSS.1095 |
The mounted resource is not ready. |
The mounted resource is not ready. |
403 |
FSS.1096 |
The file sharing protocol of the mounted resource is not NFS. |
The file sharing protocol of the mounted resource is not NFS. |
400 |
FSS.1101 |
Invalid trigger type. |
Invalid trigger type. |
400 |
FSS.1102 |
Invalid SMN trigger parameters. |
Invalid SMN trigger parameters. |
400 |
FSS.1106 |
Invalid OBS trigger parameters. |
Invalid OBS trigger parameters. |
400 |
FSS.1107 |
Invalid APIG trigger parameters. |
Invalid APIG trigger parameters. |
403 |
FSS.1108 |
The bucket configuration of the current trigger conflicts with that of an existing OBS trigger. |
The bucket configuration of the current trigger conflicts with that of an existing OBS trigger. |
400 |
FSS.1109 |
Invalid timer trigger parameters. |
Invalid timer trigger parameters. |
404 |
FSS.1111 |
The Kafka resource cannot be found. |
The Kafka resource cannot be found. |
400 |
FSS.1112 |
The Kafka trigger parameters are invalid. |
Invalid Kafka trigger parameters. |
400 |
FSS.1113 |
The username and password must be specified because Kafka SASL_SSL is enabled. |
The username and password must be specified because Kafka SASL_SSL is enabled. |
400 |
FSS.1114 |
The subnet of the function must be the same as that of the Kafka instance. |
The subnet of the function is different from that of the Kafka instance. |
503 |
FSS.1115 |
The network is unreachable. |
The network is unreachable. |
400 |
FSS.1116 |
Kafka instance configuration error. Please check the username and password. |
Kafka instance configuration error. Check the username and password. |
400 |
FSS.1117 |
Failed to query messages from the Kafka instance. |
Failed to query messages from the Kafka instance. |
401 |
FSS.1118 |
Access denied. |
Access denied. The user is not in the whitelist. |
403 |
FSS.1121 |
Forbidden |
Access denied. Check whether the corresponding agency has been configured. |
403 |
FSS.1122 |
Forbidden |
Access denied. Check whether the corresponding agency has been configured. |
403 |
FSS.1123 |
The number of pull triggers exceeds the maximum allowed limit. |
The number of pull-mode triggers has reached 10. |
403 |
FSS.1124 |
The number of APIs exceeds the maximum allowed limit. |
The number of APIs exceeds the maximum allowed limit. |
403 |
FSS.1125 |
Forbidden |
Access denied. |
403 |
FSS.1126 |
You do not have permissions to call the API. |
You do not have permissions to call the API. |
403 |
FSS.1127 |
The EPS user does not have permissions to call the API. |
The EPS user does not have permissions to call the API. |
404 |
FSS.1131 |
The trigger does not exist. |
The trigger cannot be found. |
404 |
FSS.1132 |
The SMN trigger does not exist. View the SMN console. |
The SMN trigger cannot be found. |
404 |
FSS.1136 |
The OBS trigger does not exist. |
The OBS trigger cannot be found. |
404 |
FSS.1137 |
Invalid trigger type. |
The trigger type cannot be found. |
404 |
FSS.1138 |
The APIG trigger does not exist. |
The APIG trigger cannot be found. |
404 |
FSS.1140 |
The timer trigger does not exist. |
The timer trigger cannot be found. |
409 |
FSS.1141 |
The SMN trigger already exists. |
The SMN trigger already exists. |
409 |
FSS.1145 |
The OBS trigger already exists. |
The OBS trigger already exists. |
409 |
FSS.1146 |
The APIG trigger already exists. |
The APIG trigger already exists. |
409 |
FSS.1147 |
The request path already exists. |
The request path already exists. |
409 |
FSS.1148 |
The timer trigger already exists. |
The timer trigger already exists. |
409 |
FSS.1150 |
The Kafka trigger already exists. |
The Kafka trigger already exists. |
406 |
FSS.1151 |
The OBS bucket is in a different region. |
The region where the OBS bucket is located does not match the current region. |
426 |
FSS.1152 |
The selected bucket cannot be used to create a trigger. |
The selected OBS bucket cannot be used to create a trigger. |
412 |
FSS.1153 |
The triggering conditions have not been met. |
The triggering conditions have not been met. |
403 |
FSS.1154 |
Aliases of a function bound with triggers cannot be deleted. |
The aliases cannot be deleted because they are bound with triggers. |
500 |
FSS.1162 |
The operation cannot take effect immediately due to service exception. |
The operation cannot take effect immediately because the service is abnormal. |
503 |
FSS.1169 |
The network is unreachable. |
The network is unreachable. |
404 |
FSS.1171 |
The SMN topic does not exist. Create one on the SMN console. |
The SMN topic does not exist. |
400 |
FSS.1172 |
The database or collection does not exist. |
The DB instance cannot be found. |
404 |
FSS.1174 |
The Kafka trigger does not exist. |
The Kafka trigger cannot be found. |
413 |
FSS.1201 |
The request body is too large. |
The request body exceeds the maximum allowed limit. |
500 |
FSS.1202 |
The response body or callback body is invalid because they do not contain any status code. |
Invalid response body. |
500 |
FSS.1302 |
Failed to save the data. |
Failed to save the trigger data. |
400 |
FSS.1303 |
Access denied due to insufficient permissions. |
Failed to verify permission. Access denied. |
400 |
FSS.1306 |
The number of triggers exceeds the maximum allowed limit. |
Trigger threshold reached. |
400 |
FSS.1307 |
The trigger name already exists. |
The trigger name already exists. |
400 |
FSS.1308 |
The operation resource does not exist. |
The resource does not exist. |
400 |
FSS.1309 |
Invalid function URN. |
Invalid function URN. |
400 |
FSS.1310 |
Unauthorized user. |
Failed to obtain the user token. |
400 |
FSS.1312 |
The notification name must be specified. |
No key notification name specified. |
400 |
FSS.1313 |
The number of operation resources has reached the maximum allowed limit. |
The number of operation resources exceeds 100. |
400 |
FSS.1314 |
The operation resource must be specified. |
No operation resource specified. |
400 |
FSS.1316 |
The resource operation has already been selected. |
Duplicate operation resource. |
400 |
FSS.1317 |
The trigger name is too long. |
The trigger name is too long. |
400 |
FSS.1318 |
Invalid trigger operation. |
Invalid trigger operation. |
502 |
FSS.1319 |
Invalid trigger name. |
Invalid trigger name. |
503 |
FSS.1401 |
Failed to obtain the image information. |
Failed to obtain the image information. |
503 |
FSS.1402 |
Failed to pull the image to create a container. |
Failed to pull the image to create a container. |
503 |
FSS.1403 |
Failed to pull the image to delete a container. |
Failed to pull the image to delete a container. |
400 |
FSS.1404 |
Invalid function initializer. |
Invalid function initializer. |
400 |
FSS.1405 |
Invalid initialization timeout. |
Invalid initialization timeout. |
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