# Error Codes
When an exception (failure callback/Promise reject) is thrown when using cloud capabilities, the Error
object contains the errCode
and errMsg
. Cloud Base HTTP API response packages also contain errcode
and errmsg
. The table below provides a list of errCode
values.
Error Code | Description |
---|---|
-1 | Common error |
-401001 | SDK common error: No permission to use API |
-401002 | SDK common error: Invalid API incoming parameter |
-401003 | SDK common error: Invalid API incoming parameter type |
-402001 | SDK database error: Circular reference detected |
-403001 | SDK file storage error: File exceeds the maximum upload size |
-40400x | SDK cloud function error: Failed to call the cloud function |
-404011 | SDK cloud function error: Failed to execute the cloud function |
-501001 | Cloud resource common error: Cloud system error |
-501002 | Cloud resource common error: Cloud response timed out |
-501003 | Cloud resource common error: The number of requests exceeds the environment quota |
-501004 | Cloud resource common error: The number of concurrent requests exceeds the environment quota |
-501005 | Cloud resource common error: Environment information exception |
-501007 | Cloud resource common error: Parameter error |
-501009 | Cloud resource common error: The resource object operated is invalid or doesn't exist |
-501015 | Cloud resource common error: The read request quota is exhausted |
-501016 | Cloud resource common error: The write request quota is exhausted |
-501017 | Cloud resource common error: Disk space is exhausted |
-501018 | Cloud resource common error: Resource is unavailable |
-501019 | Cloud resource common error: Unauthorized operation |
-501020 | Cloud resource common error: Unknown parameter error |
-501021 | Cloud resource common error: Unsupported operation |
-502001 | Cloud resource database error: Database request failed |
-502002 | Cloud resource database error: Invalid database command |
-502003 | Cloud resource database error: No permission to perform database operations |
-502005 | Cloud resource database error: The collection doesn't exist |
-502010 | Cloud resource database error: Operation failed |
-502011 | Cloud resource database error: Operation timed out |
-502012 | Cloud resource database error: Insert failed |
-502013 | Cloud resource database error: Failed to create collection |
-502014 | Cloud resource database error: Failed to delete data |
-502015 | Cloud resource database error: Failed to query data |
-503001 | Cloud resource file storage error: Request for cloud files failed |
-503002 | Cloud resource file storage error: No permission to access cloud files |
-503003 | Cloud resource file storage error: The file doesn't exist |
-503003 | Cloud resource file storage error: Invalid signature |
-504001 | Cloud resource cloud function error: Failed to call the cloud function |
-504002 | Cloud resource cloud function error: Failed to execute the cloud function |
-601001 | WeChat backend common error: System error |
-601002 | WeChat backend common error: System parameter error |
-601003 | WeChat backend common error: System network error |
-604101 | WeChat backend cloud function error: No permission to call this API |
-604102 | WeChat backend cloud function error: Call timed out |
-604101 | WeChat backend cloud function error: Call system error |
-605101 | WeChat backend HTTP API error: Failed to parse query statement |
Note:
- When an AppID has not activated the Cloud Base service or just activated the service but has not completed the preparation process (takes 10 minutes), if
cloud.init
is called, the system reports thecloud init error: { errMsg: "invalid scope" }
error. Activate Cloud Base first if you have not done so already. If you just activated Cloud Base, try again in 10 minutes.