Error Codes of Service Integration APIs
| Status Code | Error Codes | Error Message | Description | Solution |
|---|---|---|---|---|
| 400 | APIC.7244 | Unsupported to update eip bandwidth | Unsupported to update eip bandwidth | Do not perform this operation. |
| 400 | APIC.7250 | Invalid query param | Invalid query param | Use a valid query parameter. |
| 400 | APIC.7251 | Invalid query param limit | Invalid query param limit | Use a valid limit. |
| 400 | APIC.7252 | Invalid query param next_token | Invalid query param next_token | Use a valid next_token. |
| 400 | APIC.7254 | IPv6 access not supported. | IPv6 access not supported. | Contact technical support. |
| 400 | APIC.7257 | The custom inbound port is bound to a custom domain name. | The custom inbound port is bound to a custom domain name. | Delete or modify the domain name bound to the custom inbound port. |
| 400 | APIC.9206 | create instance failed | Failed to create the instance. | If resources are insufficient, expand resources. If the network is abnormal, check the network of the corresponding service and restore the network connectivity. |
| 400 | APIC.9218 | Create instance failed due to insufficient quota. | Create instance failed due to insufficient quota. | Increase the quota and try again. |
| 400 | APIC.9219 | Create instance failed due to insufficient resources. | Create instance failed due to insufficient resources. | Expand the resource capacity and try again. |
| 400 | APIC.9220 | Failed to update inbound access address of the instance | Failed to update inbound access address of the instance | Contact technical support. |
| 400 | APIC.9221 | Inbound access address of the instance cannot be updated. | Inbound access address of the instance cannot be updated. | This operation is not supported. |
| 400 | APIC.9223 | Delete custom inbound port failed. | Delete custom inbound port failed. | Try again later or contact technical support. |
| 400 | APIC.9224 | Add custom inbound port failed. | Add custom inbound port failed. | Try again later or contact technical support. |
| 400 | APIG.1000 | The token is missing. | Failed to identify the user authentication information. Re-log in or try again later. | Access with a token. |
| 400 | APIG.1119 | No permissions to perform operations on this method. | No permissions to perform operations on this method. | Obtain the corresponding fine-grained permission first. |
| 400 | APIG.1120 | No permissions to create ELB channels. | No permissions to create ELB channels. | The ELB channel to be operated must be under your own account. If the ELB channel is under another account, you must obtain the authorization first. |
| 400 | APIG.1201 | The resources belong to different tenants. | The resources belong to different tenants. | Ensure that the objects to be operated belong to the same tenant. |
| 400 | APIG.2000 | Parameter error. | Incorrect request parameter {x}. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2001 | The request parameters must be specified. | Request parameter {x} must be specified. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2002 | The parameter value is too small. | The value of parameter {x} is too small. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2003 | The parameter value is too large. | The value of parameter {x} is too large. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2004 | The parameter value is outside the allowable range. | The value of parameter {x} is outside the allowable range. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2005 | The parameter is too short. | The parameter is too short. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2006 | The parameter is too long. | The parameter is too long. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2007 | Invalid length. | Invalid length. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2008 | Only letters are allowed. | Only letters are allowed. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2009 | Only digits are allowed. | Only digits are allowed. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2010 | Only letters and digits are allowed. | Only letters and digits are allowed. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2011 | Invalid parameter value. | The setting of arameter {x} does not match the rule. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2012 | Invalid parameter value. | The parameter matches an unexpected rule. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2013 | Only letters, digits, hyphens (-), and underscores (_) are allowed. | Only letters, digits, hyphens (-), and underscores (_) are allowed. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2014 | Invalid email address. | Invalid email address. | Modify the request parameter based on the returned cause. |
| 400 | APIG.2015 | Invalid IP address. | Invalid IP address. | Modify the request parameter based on possible causes. |
| 400 | APIG.2016 | The characters are not encoded using Base 64. | The characters are not encoded using Base 64. | Change the request parameter to a correct Base64-encoded character string. |
| 400 | APIG.2017 | Invalid mobile number. | Invalid mobile number. | Modify the request parameter based on possible causes. |
| 400 | APIG.2018 | Invalid telephone number. | Invalid telephone number. | Modify the request parameter based on possible causes. |
| 400 | APIG.2019 | Invalid telephone or mobile number. | Invalid telephone or mobile number. | Modify the request parameter based on possible causes. |
| 400 | APIG.2020 | Invalid postal code. | Invalid postal code. | Modify the request parameter based on possible causes. |
| 400 | APIG.2021 | The URL domain is not included in the IP address whitelist. | The URL domain is not included in the IP address whitelist: {x}. | Modify the request parameter. |
| 400 | APIG.2022 | The URL domain is included in the IP address blacklist. | The URL domain is included in the IP address blacklist: {x}. | Modify the request parameter. |
| 400 | APIG.2023 | URL domain CNAME resolution failed. | URL domain CNAME resolution failed. | Register the CNAME resolution record of the domain name first. |
| 400 | APIG.2024 | Invalid URL domain. | Invalid URL domain. | Use a correct domain name. |
| 400 | APIG.2025 | Invalid backend port number. | Invalid backend port number. | Use a correct port number. |
| 400 | APIG.2026 | The request path parameters do not match the request URI. | The request path parameters do not match the request URI. | Add the parameters contained in the request path to the request parameters. |
| 400 | APIG.2027 | The backend path parameters do not match the backend URI. | The backend path parameters do not match the backend URI. | Add the parameters contained in the backend request path to backend parameters. |
| 400 | APIG.2028 | The backend parameters are not mapped to the request parameters. | The backend parameters are not mapped to the request parameters. | Change the source in the backend parameter to a correct request parameter. |
| 400 | APIG.2030 | Bad request for debugging the API. | Bad request for debugging the API. | Use correct API debugging parameters. |
| 400 | APIG.2034 | The domain name has not been filed. File it first. | The domain name has not been filed. File it first. | File the domain name first. |
| 400 | APIG.2035 | The ICP Filing System is busy. Please try again later. | The ICP Filing System is busy. Please try again later. | Contact technical support engineers for assistance. |
| 400 | APIG.2037 | Plugin content invalid | Plugin content invalid | Modify the plugin content. |
| 400 | APIG.2038 | Invalid cron expression | Invalid cron expression | The cron expression is invalid. |
| 400 | APIG.2039 | Only boolean are allowed | Only boolean are allowed | Use a parameter of the Boolean type. |
| 400 | APIG.2041 | Invalid microservice. | Invalid microservice. | Change service_id to a valid microservice ID. |
| 400 | APIG.2042 | Invalid engine. | Invalid engine. | Change engine_id to a valid microservice engine ID. |
| 400 | APIG.2043 | Too many custom backends to take offline. | Too many custom backends to take offline. | Reduce the number of custom backends. |
| 400 | APIG.2044 | Invalid title of info | Invalid Info.title | The Info.title must meet the documents |
| 400 | APIG.2045 | Parse Servers error. The Servers must meet the documents | Servers field parsing error. Servers field is invalid | The Servers must meet the documents |
| 400 | APIG.2046 | Incorrect custom authentication timeout. | Incorrect custom authentication timeout. | Modify the custom authentication timeout. It should be less than or equal to the function execution timeout and the V2 API timeout (600s). |
| 400 | APIG.2047 | Incorrect number of retries for custom authentication. | Incorrect number of retries for custom authentication. | Set the number of custom authentication retries to a value between 0 and 10. |
| 400 | APIG.2048 | Incorrect Nacos configurations. | Incorrect Nacos configurations. | Correct the Nacos configurations. |
| 400 | APIG.2049 | The port is not in the defined custom inbound ports. | The port is not in the defined custom inbound ports. | Use the default HTTP/HTTPS port, or define a new port in the inbound rule. |
| 400 | APIG.2050 | The combination of this domain name and port already exists. | The combination of this domain name and port already exists. | Specify another domain name or port number. |
| 400 | APIG.2051 | A domain name cannot be bound with different certificates. | A domain name cannot be bound with different certificates. | Bind the same certificate. |
| 400 | APIG.2052 | SM2 certificates are supported only by gateways with SM cryptographic algorithms. | SM2 certificates are supported only by gateways with SM cryptographic algorithms. | Contact technical support to check whether gateways with SM cryptographic algorithms can be created. |
| 400 | APIG.2053 | Invalid agency. | Invalid agency. | Check whether the agency is correctly configured. |
| 400 | APIG.2055 | No agency is configured for the gateway. | No agency is configured for the gateway. | The gateway has no agency to refresh. |
| 400 | APIG.2101 | The certificate and private key do not match. | The certificate and private key do not match. | Use the matching certificate and private key. |
| 400 | APIG.2102 | The certificate has expired. | The certificate has expired. | Use a certificate that has not expired. |
| 400 | APIG.2103 | The certificate common name does not match the domain name. | The certificate common name does not match the domain name. | Ensure that the domain name in the certificate is the same as the user-defined domain name. |
| 400 | APIG.2104 | The certificate chain is not matched. | The certificate chain is not matched. | Place the server certificate at the beginning and the other certificates in sequence if a certificate chain contains multiple certificates. |
| 400 | APIG.2105 | Encrypted private keys are not supported. | Encrypted private keys are not supported. | Use an unencrypted private key. |
| 400 | APIG.2106 | Invalid certificate or private key. | Invalid certificate or private key. | Use a correct certificate and private key. |
| 400 | APIG.2108 | Microservice unavailable. | Microservice unavailable. | Change service_id to the ID of an available microservice. |
| 400 | APIG.2109 | Invalid certificate. SAN missing. | Invalid certificate. SAN missing. | Generate a new certificate that contains a SAN. |
| 400 | APIG.3073 | The IP address or IP address/CIDR mask does not exist. | The IP address or IP address/CIDR mask does not exist. | Check the IP address or IP address/CIDR mask. |
| 400 | APIG.3141 | The number of API tasks exceeds the maximum allowed limit | The number of API tasks exceeds the maximum allowed limit | Contact technical support engineers to increase the quota. |
| 400 | APIG.3145 | The number of member groups exceeds the maximum allowed limit | The number of member groups exceeds the maximum allowed limit | Contact technical support engineers to increase the quota. |
| 400 | APIG.3147 | The number of kafka log plugins exceeds the maximum allowed limit | The number of kafka log plugins exceeds the maximum allowed limit | Contact technical support engineers to increase the quota. |
| 400 | APIG.3148 | Invalid certificate. Add one that expires before January 19, 2038 03:14:07 UTC. | Invalid certificate. Add one that expires before January 19, 2038 03:14:07 UTC. | Add one that expires before January 19, 2038 03:14:07 UTC. |
| 400 | APIG.3149 | Too many MRS HBase data sources. | Too many MRS HBase data sources. | Do not perform this operation. |
| 400 | APIG.3152 | Too many MRS data sources | Too many MRS data sources | Delete excessive MRS data sources and create a new one. |
| 400 | APIG.3153 | The number of custom GeoIPs exceeds the limit. | The number of custom GeoIPs exceeds the limit. | Delete unnecessary custom GeoIPs. |
| 400 | APIG.3154 | Too many connections. | Too many connections. | Increase the APIC connection quota. |
| 400 | APIG.3201 | The API group name already exists. | The API group name already exists. | Use another name. |
| 400 | APIG.3202 | The API name already exists. | The API name already exists. | Use another name. |
| 400 | APIG.3203 | The app name already exists. | The app name already exists. | Use another name. |
| 400 | APIG.3204 | The request throttling policy name already exists. | The request throttling policy name already exists. | Use another name. |
| 400 | APIG.3205 | The environment name already exists. | The environment name already exists. | Use another name. |
| 400 | APIG.3206 | The access control policy name already exists. | The access control policy name already exists. | Use another name. |
| 400 | APIG.3207 | The signature key name already exists. | The signature key name already exists. | Use another name. |
| 400 | APIG.3208 | The VPC channel name already exists. | The VPC channel name already exists. | Use another name. |
| 400 | APIG.3209 | The parameter name already exists. | The parameter name already exists. | Use another name. |
| 400 | APIG.3210 | The backend policy name already exists. | The backend policy name already exists. | Use another name. |
| 400 | APIG.3211 | The authorizer name already exists. | The authorizer name already exists. | Use another name. |
| 400 | APIG.3212 | he identity source name already exists. | he identity source name already exists. | Use another name. |
| 400 | APIG.3213 | The API tag name already exists. | The API tag name already exists. | Use another name. |
| 400 | APIG.3215 | The backend API name already exists. | The backend API name already exists. | Use another name. |
| 400 | APIG.3216 | The response name already exists. | The response name already exists. | Use another name. |
| 400 | APIG.3301 | The API already exists. | The API already exists. | Modify the API method and URL to avoid conflicts with other APIs. |
| 400 | APIG.3303 | The environment variable already exists. | The environment variable already exists. | Use another name. |
| 400 | APIG.3305 | The URL domain name already exists. | The URL domain name already exists. | Check whether the domain name has already been used, or use another domain name. |
| 400 | APIG.3306 | The IP address already exists. | The IP address already exists. | Check the IP addresses in the blacklist or whitelist, and delete duplicate ones. |
| 400 | APIG.3309 | The operation has already been performed. | The operation has already been performed. | Reduce concurrent operations or try again later. |
| 400 | APIG.3310 | The AppKey already exist. | The AppKey already exist. | Use another AppKey. |
| 400 | APIG.3311 | The AppCode already exists. | The AppCode already exists. | Use another AppCode. |
| 400 | APIG.3314 | The backend API already exists. | The backend API already exists. | Modify the method and URL of the custom backend API to avoid conflicts with other APIs. |
| 400 | APIG.3315 | The returned object name already exists. | The returned object name already exists. | Use another name. |
| 400 | APIG.3316 | The API authorization relationship already exists. | The API authorization relationship already exists. | Use other APIs or apps for authorization. |
| 400 | APIG.3317 | The sign binding relationship already exists | The sign binding relationship already exists | Check whether the signature key used by the custom backend is the same as that bound to the frontend API. |
| 400 | APIG.3318 | The plugin name already exists | The plugin name already exists | Use another name. |
| 400 | APIG.3319 | The API task name already exists | The API task name already exists | Use another name. |
| 400 | APIG.3325 | The APP quota name already exists. | The APP quota name already exists. | Use another name. |
| 400 | APIG.3326 | The vpc channel member already exists | The vpc channel member already exists | Use another backend server. |
| 400 | APIG.3328 | The vpc channel member group already exists | The vpc channel member group already exists | Use another name. |
| 400 | APIG.3330 | VPC already bound to a microservice. | VPC already bound to a microservice. | Change vpc_channel_id to another ID not bound to any microservice. |
| 400 | APIG.3331 | The orchestration rule name already exists. | The orchestration rule name already exists. | Use a unique rule name. |
| 400 | APIG.3332 | The IP address or IP address/CIDR mask already exists. | The IP address or IP address/CIDR mask already exists. | Check whether the IP address or IP address/CIDR mask is unique. |
| 400 | APIG.3459 | The api group version not match. | The api group version not match. | Modify the version to match the group type. |
| 400 | APIG.3469 | All the members must bound to member group or not | All the members must bound to member group or not | Bind all servers of the load balance channel to the server group or unbind all the servers from the server group. |
| 400 | APIG.3471 | No permissions to perform operations on this type of VPC channel. | No permissions to perform operations on this type of VPC channel. | Do not perform this operation. |
| 400 | APIG.3472 | The instance has been used by another VPC. | The instance has been used by another VPC. | Release the relationship with another VPC |
| 400 | APIG.3473 | The load balancer has already been bound to another endpoint service. | The load balancer has already been bound to another endpoint service. | Do not perform this operation. |
| 400 | APIG.3474 | The API group ID in the URL does not match the API group to which the URL domain has been bound. | The API group ID in the URL does not match the API group to which the URL domain has been bound. | Change the group in the URL to the group bound to the domain name. |
| 400 | APIG.3475 | The API group ID in the URL does not match the API group to which the certificate has been bound. | The API group ID in the URL does not match the API group to which the certificate has been bound. | Change the group in the URL to the group bound to the certificate. |
| 400 | APIG.3476 | The domain ID in the URL does not match the domain to which the certificate has been bound. | The domain ID in the URL does not match the domain to which the certificate has been bound. | Change the domain name in the URL to the domain name bound to the certificate. |
| 400 | APIG.3477 | The authorizer type and API do not match. | The authorizer type and API do not match. | Use the correct custom authorizer type. |
| 400 | APIG.3479 | No permissions to perform opreations on this ROMA integration application. | No permissions to perform opreations on this ROMA integration application. | Modify the resources to belong to the same application. |
| 400 | APIG.3489 | The data source type is not supported. | The data source type is not supported. | Use the correct data source type. |
| 400 | APIG.3494 | The backend of API is livedata and cannot change. | The backend of API is livedata and cannot change. | Cancel the custom backend deployment, and try again after modification. |
| 400 | APIG.3499 | The API task logs cannot be queried when the API task status is init | The API task logs cannot be queried when the API task status is init | Please start the API task first then query the API task logs. |
| 400 | APIG.3600 | Json or Yaml format error. | Json or Yaml format error. | Check whether the file to be imported is a YAML or JSON file and whether the file format is correct. Note: This error is also reported when an Excel file is imported. |
| 400 | APIG.3601 | The Swagger file version must be 2.0. | The Swagger file version must be 2.0. | Use a Swagger file of the 2.0 version. |
| 400 | APIG.3602 | Syntax error in the Swagger file. | Syntax error in the Swagger file. | Check the error in the Swagger file. |
| 400 | APIG.3603 | The Swagger file content is too long. | The Swagger file content is too long. | Reduce the Swagger file size. |
| 400 | APIG.3604 | Syntax error in the imported assets file. | Syntax error in the imported assets file. | Check the asset file format. |
| 400 | APIG.3605 | The number of assets exceeds the maximum allowed limit. | The number of assets exceeds the maximum allowed limit. | Reduce the number of assets. |
| 400 | APIG.3606 | Asset version transfer failed. | Asset version transfer failed. | Change the mapping between asset versions and asset formats. |
| 400 | APIG.3607 | Valid external dependencies for assets fail. | Valid external dependencies for assets fail. | Try again or contact technical support engineers to check whether the data plane synchronization is abnormal. |
| 400 | APIG.3610 | When the backend uses the load balance channel, the number of retry count cannot exceed the number of available backend servers in the load balance channel | When the backend uses the load balance channel, the number of retry count must be less than the number of available backend servers in the load balance channel | Change the number of retry times to a value less than the number of available backend servers of the load balance channel. |
| 400 | APIG.3710 | The VPC channel is being used by another third_auth plugin | The VPC channel is being used by another third_auth plugin | Unbind the third-party plug-in from the load balance channel, and then delete the load balance channel. |
| 400 | APIG.3715 | A domain name can only be bound with CA certificates of the same algorithm type. | A domain name can only be bound with CA certificates of the same algorithm type. | Unbind the existing CA certificates and try again. |
| 400 | APIG.3717 | Two-way TLS authentication not supported for HTTP or GRPC backend requests. | Two-way TLS authentication not supported for HTTP or GRPC backend requests. | Disable two-way TLS authentication first. |
| 401 | APIC.7100 | Token missing. | Token missing. | Access with a token. |
| 401 | APIC.7101 | Token expired. | Token expired. | Obtain a token again for access. |
| 401 | APIC.7102 | Incorrect token or token resolution failure. | Incorrect token or token resolution failure. | Contact technical support engineers to check whether the token encryption/decryption setting is abnormal. |
| 401 | APIC.7103 | Token contains no project information. | Token contains no project information. | Use the project information to obtain the token. |
| 401 | APIC.7104 | Token contains no domain information. | Token contains no project information. | Use the tenant project information to obtain the token. |
| 401 | APIC.7105 | Token contains no user information. | Token contains no user information. | Use the user information to obtain the token. |
| 401 | APIC.7107 | Token contains no role information. | Token contains no role information. | Use the role information to obtain the token. |
| 401 | APIG.1001 | The token has expired. | The token has expired. | Obtain a token again for access. |
| 401 | APIG.1002 | Incorrect token or token resolution failed. | Incorrect token or token resolution failed. | Use a correct token to access the system. |
| 401 | APIG.1003 | The token does not contain project information. | The token does not contain project information. | Access using a token containing project information. |
| 401 | APIG.1005 | No permissions to request this method. | No permissions to request this method. | Access using a token that contains the required permissions. |
| 401 | APIG.1009 | The token does not contain user information. | The token does not contain user information. | Access using a token containing user information. |
| 401 | APIG.1010 | PDP server connection failed. | PDP server connection failed. | Contact technical support engineers to view the management plane logs and check whether connection of the IAM fine-grained authentication server is abnormal. |
| 401 | APIG.1144 | No permissions to perform operations on this API task | No permissions to perform operations on this API task | The scheduled task to be operated must be under your own account. If the task is under another account, you must obtain the authorization first. |
| 401 | APIG.1300 | No permissions to perform operations on this project | No permissions to perform operations on this project | Use a token for the correct project. |
| 401 | APIG.3497 | The ROMA APP to which the API task belongs cannot be changed | The ROMA APP to which the API task belongs cannot be changed | Do not perform this operation. |
| 401 | APIG.3498 | The API task cannot be operated when the API task status is started | The API task cannot be operated when the API task status is started | Stop the scheduled task and try again. |
| 401 | APIG.3700 | The API task status is started and does not need to be started again | The API task status is started and does not need to be started again | Stop the scheduled task and try again. |
| 401 | APIG.3701 | The API task status is init or stopped and does not need to be stopped again | The API task status is init or stopped and does not need to be stopped again | Start the scheduled task and try again. |
| 403 | APIC.7106 | No permissions to request for the method. | No permissions to request for the method. | Access using a token that contains the required permissions. |
| 403 | APIC.7109 | Account restricted. No permissions to request the POST method. | Account restricted. No permissions to request the POST method. | Cancel restrictions on the account first. |
| 403 | APIC.7110 | Readonly account. No permissions to request any method except GET. | Readonly account. No permissions to request any method except GET. | Contact the account administrator to configure other permissions. |
| 403 | APIC.7111 | Token not belong to the project in URI. | Token not belong to the project in URI. | Use a correct token to access the system. |
| 403 | APIC.7130 | No permissions for operating the instance | No permissions for operating the instance | Use the correct project ID. |
| 403 | APIC.7403 | The number of custom inbound ports has reached the maximum. | The number of custom inbound ports has reached the maximum. | Increase the quota for custom inbound ports. |
| 403 | APIG.1020 | Insufficient permissions. | Insufficient permissions. | Grant the read and write permissions to the user. |
| 403 | APIG.1101 | No permissions to perform operations on this API group. | No permissions to perform operations on this API group. | The API group to be operated must be under your own account. If the API group is under another account, you must obtain the authorization first. |
| 403 | APIG.1102 | No permissions to perform operations on this API. | No permissions to perform operations on this API. | The API to be operated must be under your own account. If the API is under another account, you must obtain the authorization first. |
| 403 | APIG.1103 | No permissions to perform operations on this environment. | No permissions to perform operations on this environment. | The environment to be operated must be under your own account. If the environment is under another account, you must obtain the authorization first. |
| 403 | APIG.1104 | No permissions to perform operations on this app. | No permissions to perform operations on this app. | The application to be operated must be under your own account. If the application is under another account, you must obtain the authorization first. |
| 403 | APIG.1105 | No permissions to perform operations on this request throttling policy. | No permissions to perform operations on this request throttling policy. | The request throttling policy to be operated must be under your own account. If the request throttling policy is under another account, you must obtain the authorization first. |
| 403 | APIG.1106 | No permissions to perform operations on this access control policy. | No permissions to perform operations on this access control policy. | The access control policy to be operated must be under your own account. If the access control policy is under another account, you must obtain the authorization first. |
| 403 | APIG.1109 | No permissions to perform operations on this app authorization record. | No permissions to perform operations on this app authorization record. | The app authorization to be operated must be under your own account. If the app authorization is under another account, you must obtain the authorization first. |
| 403 | APIG.1110 | No permissions to perform operations on this environment variable. | No permissions to perform operations on this environment variable. | The environment variable to be operated must be under your own account. If the environment variable is under another account, you must obtain the authorization first. |
| 403 | APIG.1112 | No permissions to perform operations on this signature key. | No permissions to perform operations on this signature key. | The signature key to be operated must be under your own account. If the signature key is under another account, you must obtain the authorization first. |
| 403 | APIG.1113 | No permissions to perform operations on this VPC channel. | No permissions to perform operations on this VPC channel. | The VPC channel to be operated must be under your own account. If the VPC channel is under another account, you must obtain the authorization first. |
| 403 | APIG.1115 | No permissions to perform operations on this certificate. | No permissions to perform operations on this certificate. | The certificate to be operated must be under your own account. If the certificate is under another account, you must obtain the authorization first. |
| 403 | APIG.1136 | No permissions to perform operations on this instance. | No permissions to perform operations on this instance. | Check whether you are using the ID of the project to which the instance belongs. |
| 403 | APIG.1137 | No permissions to perform operations on this authorizer | No permissions to perform operations on this authorizer | The custom authorizer to be operated must be under your own account. If the custom authorizer is under another account, you must obtain the authorization first. |
| 403 | APIG.1138 | No permissions to perform operations on this data source. | No permissions to perform operations on this data source. | The data source to be operated must be under your own account. If the data source is under another account, you must obtain the authorization first. |
| 403 | APIG.1139 | No permissions to perform operations on this livedata API | No permissions to perform operations on this livedata API. | The backend API to be operated must be under your own account. If the backend API is under another account, you must obtain the authorization first. |
| 403 | APIG.1140 | No permissions to perform operations on this feature | No permissions to perform operations on this feature. | The feature to be operated must be under your own account. If the feature is under another account, you must obtain the authorization first. |
| 403 | APIG.1141 | No permissions to perform operations on this ROMA integration application. | No permissions to perform operations on this ROMA integration application. | Use the primary account or the sub-user who creates the ROMA integration application to grant corresponding permissions to the sub-user who needs to access the integration application. |
| 403 | APIG.1142 | No permissions to perform operations on this client quota | No permissions to perform operations on this client quota | Use the administrator account to perform operations on the client quota. |
| 403 | APIG.1143 | No permissions to perform operations on this plugin | No permissions to perform operations on this plugin | The plugin to be operated must be under your own account. If the plugin is under another account, you must obtain the authorization first. |
| 403 | APIG.1149 | No permission for this instance task. | No permission for this instance task. | Use a token of the correct project. |
| 403 | APIG.1301 | No permissions to perform operations on this domain | No permissions to perform operations on this domain | The domain to be operated must be under your own account. |
| 403 | APIG.2054 | The gateway fails to create an API to call the function. | The gateway fails to create an API to call the function. | Configure the agency on the gateway information page. |
| 403 | APIG.3066 | The roma auth tunnel does not exist. | The roma auth tunnel does not exist. | Check whether the green channel authorization type is correct. |
| 403 | APIG.3100 | The number of resources exceeds the maximum allowed limit. | The number of resources exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3101 | The number of API groups exceeds the maximum allowed limit. | The number of API groups exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3102 | The number of APIs exceeds the maximum allowed limit. | The number of APIs exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3103 | The number of apps exceeds the maximum allowed limit. | The number of apps exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3104 | The number of environments exceeds the maximum allowed limit. | The number of environments exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3105 | The number of signature keys exceeds the maximum allowed limit. | The number of signature keys exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3106 | The number of variables exceeds the maximum allowed limit. | The number of variables exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3107 | The number of request throttling policies exceeds the maximum allowed limit. | The number of request throttling policies exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3108 | The number of domain names exceeds the maximum allowed limit. | The number of domain names exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3109 | The number of VPC channels exceeds the maximum allowed limit. | The number of VPC channels exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3110 | The number of instances exceeds the maximum allowed limit. | The number of instances exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3111 | The number of parameters in req_params exceeds the maximum allowed limit. | The number of parameters in req_params exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3112 | The number of access control policies exceeds the maximum allowed limit. | The number of access control policies exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3113 | The maximum number of API backend policies has been reached. | The maximum number of API backend policies has been reached. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3114 | The maximum number of policy conditions has been reached. | The maximum number of policy conditions has been reached. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3116 | The number of custom authorizers exceeds the maximum allowed limit. | The number of custom authorizers exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3117 | The number of identity sources exceeds the maximum allowed limit. | The number of identity sources exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3125 | The maximum number of APIs for one API group has been reached. | The maximum number of APIs for one API group has been reached. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3127 | The number of APIs has reached the upper limit. A maximum of xxx APIs can be imported at a time. | The number of APIs has reached the upper limit. A maximum of xxx APIs can be imported at a time. | Reduce the number of APIs to be imported. |
| 403 | APIG.3131 | The number of AppCodes exceeds the maximum allowed limit. | The number of AppCodes exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3133 | The number of API tags exceeds the maximum allowed limit. | The number of API tags exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3134 | The number of livedata APIs exceeds the maximum allowed limit. | The number of livedata APIs exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3135 | The number of API scripts exceeds the maximum allowed limit. | The number of API scripts exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3136 | The number of responses exceeds the maximum allowed limit. | The number of responses exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3138 | The number of Configurations for one APP exceeds the maximum allowed limit. | The number of Configurations for one APP exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3139 | The number of APP quotas exceeds the maximum allowed limit. | The number of APP quotas exceeds the maximum allowed limit. | Contact technical support engineers to increase the quota. |
| 403 | APIG.3140 | The number of plugins exceeds the maximum allowed limit | The number of plugins exceeds the maximum allowed limit | Contact technical support engineers to increase the quota. |
| 403 | APIG.3150 | The number of orchestration rules exceeds the maximum. | The number of orchestration rules exceeds the maximum. | Contact technical support to increase the quota of orchestration rules. |
| 403 | APIG.3151 | The number of orchestration rules bound to the API exceeds the maximum. | The number of orchestration rules bound to the API exceeds the maximum. | Contact technical support to increase the quota of orchestration rules that can be bound to the API. |
| 403 | APIG.3483 | The API is deployed and cannot be deleted. | The API is deployed and cannot be deleted. | Cancel the deployment and try again. |
| 403 | APIG.3484 | The API status does not support deployment. | The API status does not support deployment. | Develop the API and then deploy it. |
| 403 | APIG.3486 | The API status does not support undeployment. | The API status does not support undeployment. | Complete API deployment and try again. |
| 404 | APIC.7302 | Instance not found | Instance not found | Check whether the instance exists, and use the correct instance ID. |
| 404 | APIG.3001 | The API group does not exist. | The API group does not exist. | Check whether the group exists. |
| 404 | APIG.3002 | The API does not exist. | The API does not exist. | Check whether the API exists. |
| 404 | APIG.3003 | The environment does not exist. | The environment does not exist. | Check whether the environment exists. |
| 404 | APIG.3004 | The app does not exist. | The app does not exist. | Check whether the application exists. |
| 404 | APIG.3005 | The request throttling policy does not exist. | The request throttling policy does not exist. | Check whether the request throttling policy exists. |
| 404 | APIG.3006 | The access control policy does not exist. | The access control policy does not exist. | Check whether the access control policy exists. |
| 404 | APIG.3007 | The configuration does not exist. | The configuration does not exist. | Check whether the configuration exists. |
| 404 | APIG.3008 | The excluded configuration does not exist. | The excluded configuration does not exist. | Check whether excluded configuration exists. |
| 404 | APIG.3009 | The app authorization record does not exist. | The app authorization record does not exist. | Check whether the app authorization exists. |
| 404 | APIG.3010 | The access control policy binding record does not exist. | The access control policy binding record does not exist. | Check whether the access control policy binding record exists. |
| 404 | APIG.3011 | The environment variable does not exist. | The environment variable does not exist. | Check whether the environment variable exists. |
| 404 | APIG.3012 | The request throttling policy binding record does not exist. | The request throttling policy binding record does not exist. | Check whether the request throttling policy binding record exists. |
| 404 | APIG.3013 | The excluded request throttling configuration does not exist. | The excluded request throttling configuration does not exist. | Check whether the special configuration of the request throttling policy exists. |
| 404 | APIG.3015 | The API publication record does not exist. | The API publication record does not exist. | Check whether the API release record exists. |
| 404 | APIG.3017 | The signature key does not exist. | The signature key does not exist. | Check whether the signature key exists. |
| 404 | APIG.3018 | The signature key binding record does not exist. | The signature key binding record does not exist. | Check whether the signature key binding record exists. |
| 404 | APIG.3019 | The function URN does not exist. | The function URN does not exist. | Check whether the function URN exists. |
| 404 | APIG.3020 | The URL domain does not exist. | The URL domain does not exist. | Check whether the group domain name exists. |
| 404 | APIG.3021 | The SSL certificate does not exist. | The SSL certificate does not exist. | Check whether the SSL certificate exists. |
| 404 | APIG.3022 | The API version does not exist. | The API version does not exist. | Check whether the API version exists. |
| 404 | APIG.3023 | The VPC channel does not exist. | The VPC channel does not exist. | Check whether the load balance channel exists. |
| 404 | APIG.3024 | The instance does not exist. | The instance does not exist. | Check whether the instance exists in the load balance channel. |
| 404 | APIG.3025 | The certificate does not exist. | The certificate does not exist. | Check whether the certificate exists. |
| 404 | APIG.3030 | The instance does not exist | The instance does not exist | Check whether the instance exists. |
| 404 | APIG.3064 | Roma app and api relation not found. | Roma app and api relation not found. | Contact technical support engineers for assistance. |
| 404 | APIG.3065 | Roma app authorize relation not found. | Roma app authorize relation not found. | Contact technical support engineers for assistance. |
| 404 | APIG.3067 | The app quota does not exist. | The app quota does not exist. | Check whether the client quota exists. |
| 404 | APIG.3068 | The plugin does not exist. | The plugin does not exist | Check whether the plugin exists. |
| 404 | APIG.3069 | The plugin binding record does not exist | The plugin binding record does not exist | Check whether the plugin binding record exists. |
| 404 | APIG.3071 | The member group does not exist | The member group does not exist | Check whether the server group of the load balance channel exists. |
| 404 | APIG.3072 | The specified task does not exist | The specified task does not exist | The specified task does not exist |
| 404 | APIG.3081 | Authorizer not found | Authorizer not found | Check whether the custom authorizer exists. |
| 404 | APIG.3082 | The AppCode does not exist. | The AppCode does not exist. | Check whether the AppCode exists. |
| 404 | APIG.3083 | The data source does not exist. | The data source does not exist. | Check whether the data source exists. |
| 404 | APIG.3084 | The livedata API does not exist | The livedata API does not exist | Check whether the custom backend API exists. |
| 404 | APIG.3087 | The feature configuration does not exist | The feature configuration does not exist | Check whether the feature exists. |
| 404 | APIG.3088 | Deployment information of the backend API does not exist. | Deployment information of the backend API does not exist. | Check whether the API deployment record exists. |
| 404 | APIG.3089 | The response does not exist | The response does not exist | Check whether the gateway response exists. |
| 404 | APIG.3091 | The APP configuration does not exist | The APP configuration does not exist | Check whether the application configuration exists. |
| 404 | APIG.3092 | The ECS does not exist | The ECS does not exist | Check whether the ECS is deleted or the entered ID is incorrect. |
| 404 | APIG.3093 | The API task does not exist | The API task does not exist | Check whether the scheduled task exists. |
| 404 | APIG.3094 | Instance task does not exist. | Instance task does not exist. | Instance task is deleted or task ID is invalid. |
| 404 | APIG.3095 | The orchestrations does not exist | The orchestrations does not exist | Check whether the orchestration rule corresponding to orchestration_id in the request parameter exists. |
| 404 | APIG.3096 | The orchestrations map does not exist | The orchestrations map does not exist | Contact technical support. |
| 404 | APIG.3097 | The binding record of this SSL certificate and domain name does not exist. | The binding record of this SSL certificate and domain name does not exist. | Check whether the binding record exists. |
| 404 | APIG.9996 | The request URL does not exist | The request URL does not exist | Contact technical support engineers to view the management plane logs. |
| 409 | APIC.7709 | The egress eip has been opened | The egress eip has been opened | Close the egress eip, and try again |
| 409 | APIC.7711 | Public inbound access is enabled for the instance | Public inbound access is enabled for the instance. | Disable public inbound access and try again. |
| 409 | APIG.3411 | The APIs belong to different tenants. | The APIs belong to different tenants. | Authorizing access to APIs of another tenant is not allowed. Select other APIs. |
| 409 | APIG.3414 | The VPC channel is already being used by another API. | The VPC channel is already being used by another API. | Before deleting the load balance channel, delete the API bound to the load balance channel. |
| 409 | APIG.3415 | The API group cannot be deleted because it contains APIs. | The API group cannot be deleted because it contains APIs. | Delete APIs from the group and then delete the group. |
| 409 | APIG.3416 | The API cannot be deleted because it has been published. | The API cannot be deleted because it has been published. | Take the API offline and then delete the API. |
| 409 | APIG.3418 | The environment contains published APIs. | The environment contains published APIs. | Take APIs offline in this environment, and then try again. |
| 409 | APIG.3457 | Cannot operate configuration of current app. | The configuration name already exists. | Change the configuration name. |
| 409 | APIG.3460 | The ld api cannot be offlined for binding to an authorizer | The ld api cannot be offlined for binding to an authorizer | Delete the custom authorizer bound to the custom backend and then cancel deployment of the backend. |
| 409 | APIG.3463 | An API with the same path of the current API has already attached with another cors plugin | An API with the same path of the current API has already attached with another cors plugin | Unbind the plugin bound to the API |
| 409 | APIG.3464 | The allow methods of the cors plugin do not contain api method | The allow methods of the cors plugin do not contain api method | Add the API method to the allow methods of the CORS plugin |
| 409 | APIG.3465 | The allow methods of the cors plugin do not contain the method of attached API | The allow methods of the cors plugin do not contain the method of attached API | Do not perform this operation. |
| 409 | APIG.3466 | An OPTIONS API with the same path of the current API already exists | An OPTIONS API with the same path of the current API already exists | Delete the OPTIONS API with the same path of the current API. |
| 409 | APIG.3467 | An API with the same path of the current API has already attached with a cors plugin | An API with the same path of the current API has already attached with a cors plugin | No need to publish this OPTIONS API. |
| 409 | APIG.3470 | The API cannot be operated because it has been used by another API task | The API cannot be operated because it has been used by another API task | Delete the scheduled task bound to the API, and then try again. |
| 409 | APIG.3478 | The authorizer has been used by certain APIs. | The authorizer has been used by certain APIs. | Unbind all APIs from the custom authorizer and then delete it. |
| 409 | APIG.3482 | The default API group cannot be deleted. | The default API group cannot be deleted. | Do not perform this operation. |
| 409 | APIG.3490 | The API deployment group ID cannot be changed. | The API deployment group ID cannot be changed. | Cancel the deployment before modifying the group ID. |
| 409 | APIG.3491 | The default response cannot be deleted. | The default response cannot be deleted. | Do not perform this operation. |
| 409 | APIG.3492 | The default response name cannot be modified. | The default response name cannot be modified. | Do not perform this operation. |
| 409 | APIG.3703 | Roma app id of the plugin must be the same with roma app id of the api | Roma app id of the plugin must be the same with roma app id of the api | Modify the plugin to use the same application as the API. |
| 409 | APIG.3707 | Only published APIs can be bound with plug-ins. | Only published APIs can be bound with plug-ins. | Publish the API and try again. |
| 409 | APIG.3708 | The key usage of the certificate does not match | The key usage of the certificate does not match | Use matched key usage |
| 409 | APIG.3709 | The signature algorithm of the certificate does not match | The signature algorithm of the certificate does not match | Change signature algorithm type |
| 409 | APIG.3711 | A configuration parameter can be modified only once per minute. | A configuration parameter can be modified only once per minute. | Try again after 1 minute. |
| 409 | APIG.3712 | User domain does not match. | User domain does not match. | Check the domain info. |
| 409 | APIG.3716 | The orchestration rule is currently in use by another API. | The orchestration rule is currently in use by another API. | Unbind the orchestration rule from the API. |
| 409 | APIG.3718 | An instance task is currently being processed. | An instance task is currently being processed. | Start a new task after the current one is complete. |
| 409 | APIG.3720 | The default group cannot be updated. | The default group cannot be updated. | This operation is not allowed. |
| 412 | APIG.3447 | The access control policy has been bound to APIs | The access control policy has been bound to APIs | Before deleting the access control policy, delete the binding relationship of access control policy and API. |
| 412 | APIG.3451 | The request throttling policy has been bound to APIs. | The request throttling policy has been bound to APIs. | Before deleting the request throttling policy, delete the binding relationship of request throttling policy and API. |
| 412 | APIG.3456 | Cannot operate configuration of current app. | Cannot operate configuration of current app. | Use an integration application. |
| 412 | APIG.3458 | The feature is not supported by current instance. | The feature is not supported by current instance. | Contact technical support engineers to upgrade the instance. |
| 412 | APIG.3468 | The member group cannot be deleted because it contains members | The member group cannot be deleted because it contains members | Delete the servers in the server group of the load balance channel, and then try again. |
| 412 | APIG.3480 | The signature key has been bound to APIs. | The signature key has been bound to APIs. | Unbind all APIs from the signature key and then delete it. |
| 412 | APIG.3481 | The app has been bound to APIs. | The app has been bound to APIs. | Unbind the app from all APIs, and then try again. |
| 412 | APIG.3488 | The signature has already binded to backend APIs. | The signature has already binded to backend APIs. | Unbind the signature key from all custom backends, and then try again. |
| 412 | APIG.3713 | orchestration_mapped_param cannot be modified. | orchestration_mapped_param cannot be modified. | Do not modify orchestration_mapped_param. |
| 412 | APIG.3714 | The backend request protocol does not support SM cryptographic algorithms. | The backend request protocol does not support SM cryptographic algorithms. | Change the protocol to HTTPS. |
| 428 | APIG.3462 | The plugin has already been attached to APIs | The plugin has already been attached to APIs | Do not perform this operation. |
| 429 | APIG.9008 | Too many requests. | Too many requests. | Try again later. |
| 500 | APIC.7253 | Internal configuration error. | Internal configuration error. | Check the internal configuration. |
| 500 | APIC.9999 | Internal server error. | Internal server error. | Contact technical support engineers to view the management plane logs and locate the error. |
| 500 | APIG.1029 | PDP5 cannot be connected. | PDP5 cannot be connected. | Check the PDP5 connection. |
| 500 | APIG.3500 | Failed to synchronize data to etcd. | Failed to synchronize data to etcd. | Contact technical support engineers to view the management plane logs and check whether the network between the management plane and the data plane etcd is normal. |
| 500 | APIG.3501 | Failed to synchronize data to the instance. | Failed to synchronize data to the instance. | Contact technical support engineers to view the management plane logs and check whether the network between the management plane and the data plane LDA is normal. |
| 500 | APIG.3503 | API testing failed. | API testing failed. | Contact technical support engineers to view the management plane logs and check whether the network between the management plane and the data plane LDA is normal. |
| 500 | APIG.9002 | Invalid function URN. | Invalid function URN. | Use a correct function URN. |
| 500 | APIG.9003 | Statistics Center request failed. | Statistics Center request failed. | Contact technical support engineers to view the management plane logs and check whether the Statistics Center network is abnormal. |
| 500 | APIG.9004 | IAM request failed. | IAM request failed. | Contact technical support engineers to view the management plane logs and check whether the IAM network is abnormal. |
| 500 | APIG.9005 | VPC request failed. | VPC request failed. | Contact technical support engineers to view the management plane logs and check whether the VPC network is abnormal. |
| 500 | APIG.9006 | DNS request failed. | DNS request failed. | Contact technical support engineers to view the management plane logs and check whether the DNS network is abnormal. |
| 500 | APIG.9009 | ROMA Quartz request failed. | ROMA Quartz request failed. | Contact technical support engineers to view the management plane logs and check whether connection of the ROMA Quartz server is abnormal. |
| 500 | APIG.9013 | Synchronize CCMS data failed | Synchronize CCMS data failed | Contact technical support. |
| 500 | APIG.9999 | System error. | System error. | Contact technical support engineers to view the management plane logs and check whether the database connection is abnormal. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
