Error Codes
When developing projects with Makers, you may encounter various errors. If a problem occurs when your site is accessed, the page will display an error code and a brief description. These errors may involve project-level access issues or deployment-level status exceptions. This chapter provides specific solutions for common error scenarios.
Error Code List
Status Code | Error Codes | Description |
400 | - | Agent request header makers-conversation-id is invalid or missing. |
401 | UNAUTHORIZED | Preview URL authentication information expired |
404 | NOT_FOUND | The site does not exist |
410 | DELETED | The deployment has been deleted |
413 | CLOUD_FUNCTION_PAYLOAD_TOO_LARGE | Cloud Functions request size exceeds limit |
423 | DEPLOYING | The project is being deployed |
424 | FAILED | Project deployment failed |
429 | - | Agent concurrent session quantity exceeds the limit. |
429 | RATE_LIMIT_EXCEEDED | Request frequency exceeds the limit. |
451 | UNAVAILABLE | Project has been banned |
500 | CLOUD_FUNCTION_RESPONSE_PAYLOAD_TOO_LARGE | Cloud Functions response size exceeds limit |
| INTERNAL_CLOUD_FUNCTION_ERROR | Cloud Functions internal error |
| INTERNAL_CLOUD_FUNCTION_INVOCATION_FAILED | Cloud Functions internal call failed |
| INTERNAL_CLOUD_FUNCTION_NOT_READY | Cloud Functions initialization failed |
502 | CLOUD_FUNCTION_INVOCATION_FAILED | Cloud Functions call failed |
503 | CLOUD_FUNCTION_SERVICE_UNAVAILABLE | Cloud Functions service unavailable |
504 | CLOUD_FUNCTION_INVOCATION_TIMEOUT | Cloud Functions call timeout |
511 | EDGE_FUNCTION_INVOCATION_LIMIT_EXCEEDED | Edge Functions invocation limit exceeded |
512 | CLOUD_FUNCTION_INVOCATION_LIMIT_EXCEEDED | Cloud Functions invocation limit exceeded |
Error Code Details
400 - Invalid Request Header
Requests routed to Agent (
agent-node / agent-python) must carry a valid makers-conversation-id request header. Otherwise, a 400 error is returned. The request header requirements are: required, a length of 6 to 36 characters, and only the characters 0-9, a-z, A-Z, -, _, and . are allowed. Please check and correct the request header, then retry.401 - Authentication Information Expired UNAUTHORIZED
To ensure content compliance, the following rules must be followed when Makers sites are accessed via project domain and deployment domain:
1. The project acceleration region is set to "Chinese mainland availability zone" or "global availability zone (including Chinese mainland)":
1.1 You must use the system-generated preview URL to access it. The link validity period is 3 hr. A 401 error will return after timeout.
1.2 You can periodically update valid links via the preview button in the upper right corner of the project overview interface through the Console.
2. The project acceleration region is set to "global availability zone (excluding Chinese mainland)":
2.1 Non-Chinese mainland network environment has direct access. Chinese mainland network environment will return a 401 error.
It is recommended to bind custom domain name to establish a stable access channel. No ICP Filing Registration is required in global availability zones (excluding Chinese mainland).
404 - Site Not Found NOT_FOUND
Please confirm whether the project domain or deployment domain you are accessing is correct.
410 - Deployment Deleted DELETED
When you delete a deployment record and then try again to access the deployment domain, a 410 error will be returned. The deployment may be deleted due to version update, resource optimization or management need. The deleted deployment cannot be recovered. You can choose to create a new deployment.
413 - Request Size Exceeds Limit CLOUD_FUNCTION_PAYLOAD_TOO_LARGE
Cloud Functions request event size exceeds limit, try simplifying function input. If related files are imported, recommend uploading files to Tencent Cloud COS.
423 - Project Is Being Deployed DEPLOYING
If the project is undergoing first deployment, wait patiently until after deployment is completed and then visit again. If it is not the first deployment, you can still access the project, but you will see the old version. After the new deployment is completed, the latest version can be accessed.
424 - Deployment Failed FAILED
A 424 error will occur if there are errors or other reasons during the project build process that cause deployment failure.
Common failure reasons include:
Script error in build.
Missing dependency or version incompatibility.
Resource limit (for example, insufficient memory).
Please view the detailed deployment record of the corresponding project in the console to obtain logs and understand the specific reason for failure. After fixing issues, you can recreate the deployment.
429 - Too Many Requests
Concurrent Session Limit Exceeded (Agent Route Only): When the number of concurrent sessions for a project reaches the limit, new Agent requests are rejected and return a 429 error (response header
Retry-After: 10) with the message "Too many concurrent requests for this zone". A session is uniquely identified by makers-conversation-id. Reusing the same ID within its validity period does not occupy a new concurrent slot. For the specific concurrent limit, see Limits and Quotas.Request Rate Limit Exceeded
RATE_LIMIT_EXCEEDED: All site requests are subject to a global rate limit. When the limit is exceeded, a 429 error is returned (response header Retry-After: 60) with the message "Too many requests. Please try again later."When encountering a 429 error, retry after backing off for the duration specified in the
Retry-After response header.451 - Project Has Been Banned UNAVAILABLE
The project has been banned and cannot be accessed due to violation of platform rules, such as involving illegal content (involving pornography, politics, etc.). Please ensure that your content complies with laws and regulations and platform regulations. If you consider this a misjudgment, please contact us through the community or customer service to get more information.
500
Response Size Exceeds Limit CLOUD_FUNCTION_RESPONSE_PAYLOAD_TOO_LARGE
Cloud Functions response size exceeds limit, adjust function return value and try again after.
Internal Error INTERNAL_CLOUD_FUNCTION_ERROR
Cloud Functions internal error, please retry later. If still unresolved, contact us or submit a ticket.
Internal Function Call Failed INTERNAL_CLOUD_FUNCTION_INVOCATION_FAILED
Cloud Functions internal execution failed, please retry later. If still unresolved, contact us or submit a ticket.
Function Not Ready INTERNAL_CLOUD_FUNCTION_NOT_READY
Cloud Functions not ready, please retry later. If still unresolved, contact us or submit a ticket.
502 - Function Call Failed CLOUD_FUNCTION_INVOCATION_FAILED
Cloud Functions call failed, usually returned when your code execution error occurs. Check code according to the error information. For more information, view function log in console.
503 - Function Service Unavailable CLOUD_FUNCTION_SERVICE_UNAVAILABLE
Cloud Functions service unavailable, check business code logic has a memory leak.
504 - Function Call Timeout CLOUD_FUNCTION_INVOCATION_TIMEOUT
Cloud Functions call timeout, check business code execution duration whether exceeds platform limitation.
511 - Edge Function Call Limit Exceeded EDGE_FUNCTION_INVOCATION_LIMIT_EXCEEDED
Edge Functions invocation limit exceeded. Wait for the next period usage recovery, or contact us or submit a ticket.
512 - Function Call Limit Exceeded CLOUD_FUNCTION_INVOCATION_LIMIT_EXCEEDED
Cloud Functions invocation limit exceeded. Wait for the next period usage recovery, or contact us or submit a ticket.
FAQs
Q: I encountered error codes not mentioned above. What should I do?
A: If you encounter an error code not covered in the document, record the error code and your steps, then contact us for help.
Q: How to prevent 401 errors caused by the expiration of the preview URL?
A: The best method is to add a custom domain to your project. This way you can always access your project through that domain, independent of the preview URL with timeliness.
Q: My project has been displaying a 423 error (being deployed), but it seems to have lasted for a long time. Is this normal?
A: Normally, the deployment process should be completed within minutes. If you find the deployment time unusually long, suggest checking your deployment log to see if there is any error information. If the problem persists, contact us.
- Error Code List
- Error Code Details
- 400 - Invalid Request Header
- 401 - Authentication Information Expired
- 404 - Site Not Found
- 410 - Deployment Deleted
- 413 - Request Size Exceeds Limit
- 423 - Project Is Being Deployed
- 424 - Deployment Failed
- 429 - Too Many Requests
- 451 - Project Has Been Banned
- 500
- 502 - Function Call Failed
- 503 - Function Service Unavailable
- 504 - Function Call Timeout
- 511 - Edge Function Call Limit Exceeded
- 512 - Function Call Limit Exceeded
- FAQs
