If an error code is returned after the function is executed, you can find the cause and solution for the error code by referring to the following table.
Status Code and Status Message
Description
Solution
200
Success
Successful
-
400
InvalidParameterValue
The request event passed in by the event execution function is not of the JSON type.
Your account does not have the permission to manipulate this function. Make modifications as instructed in the authorization description in Permission Management Overview and try again.
402
ServiceSuspended
The service is temporarily suspended.
Your SCF service is temporarily suspended. You can refer to Payment Overdue to make changes and try again later.
404
InvalidSubnetID
The subnet ID in the network configuration of the function is exceptional.
Check whether the network configuration of the function is correct and whether the subnet ID is valid.
405
ContainerStateExited
The container exits.
Check your image or bootstrap file to see whether it can be properly started locally. If so, check whether the use limits of SCF are followed; for example, RootFS is read-only and only /tmp is writable. Local debugging command:
docker run -itd --read-only -v /tmp:/tmp
406
RequestTooLarge
The event input parameter of the function, i.e., the request event size of the function, exceeds the quota limit.
The request event size exceeds the quota limit, which is 6 MB for sync request events or 128 KB for async ones. Adjust the request event size accordingly and try again.
407
The size of response exceeds the upper limit (6MB)
The size of function response exceeds the upper limit of 6 MB.
Please adjust it and try again.
410
InsufficientBalance
Insufficient account balance
The SCF service is suspended because the Tencent Cloud account has overdue payments. Top up and try again.
429
ResourceLimit
The container request rate is too high and exceeds the limit due to concurrency surges.
The default maximum speed of elastic concurrency expansion (function burst) for each account is 500 concurrent instances per region per minute. During a sudden concurrency surge, if there are not enough containers to carry the requests, a large number of container request actions will be triggered, and this message will be returned when the account limit is exceeded.
After assessing the function concurrency, configure provisioned concurrency for the function and prepare containers in advance to avoid sudden concurrency surges from causing the container request speed to exceed the limit.
If assessment shows that the provisioned concurrency cannot meet the needs of your business scenario, you can purchase a function package to increase the function burst in the region.
430
User code exception caught
A user code execution error occurs.
Please check the code error stack information in the invocation log provided by the SCF console, make modifications, and try again.
432
ResourceLimitReached
The account-level or region-level concurrency limit is reached.
For a function with a reserved quota configured, if the function concurrency exceeds the quota, Function [ xxx ] concurrency exceeded reserved quota xxx MB will be returned. You can assess your business needs and increase the quota or refer to Concurrency Overrun.
For a function with no reserved quota configured, if the concurrency quota actually used by the function exceeds the region-level unused concurrency quota, Function [ xxx ] concurrency exceeded region unreserved quota xxx MB will be returned. You can assess your business needs and configure a reserved quota for the function. If the remaining available quota in the corresponding region cannot meet your business needs, you can purchase a function package to increase the total concurrency quota in the region.
Please check whether a large number of time-consuming operations exists in the service code.
Set a longer timeout period on the Function configuration page. If the current timeout period has been set to the maximum value, you can create an async function as instructed in Async Execution to get a function execution duration of up to 24 hours.
Please check the code logic to see whether there is a memory leak.
Please increase the memory configuration on the Function Configuration page, or apply for a large memory on the Function Memory Configuration page to get up to 120 GB of function execution memory.
Please check whether the input parameters match the information of the function to be invoked.
Please check whether the function exists when it is invoked and whether there is any deletion action that causes the function to be invoked after deletion.
436
InvalidParameterValue
The parameter passed in for invoke does not conform to the specification.
The parameter does not conform to the specification. Modify it as instructed in Introduction and try again.
437
HandlerNotFound
The function package is loaded incorrectly.
Please check whether the compressed package is in normal status.
The function execution entry file is not found. Please make sure that the entry file is in the root directory of the decompressed code package.
Check whether the CAM authentication parameters for the function invoker are passed correctly. For more information, see the authorization description in Permission Management Overview.
442
QualifierNotFound
The specified version is not found.
The function version does not exist. Check the function version and try again.
443
UserCodeError
A user code execution error occurs.
Based on the error log on the console, check the error stack of the code and see whether the code can be executed properly.
444
PullImageFailed
Image pull fails.
Check the integrity and validity of the selected image and try again; for example, check whether it can be downloaded locally. If the problem persists, submit a ticket.
445
ContainerInitError
Container start fails.
Container start fails. Check whether your bootstrap file has been uploaded successfully and ensure that the invocation path is correct.
For an image deployment-based function, check whether the Command or Args parameter passed in the console is in the correct format. For more information, see Usage.
For a code deployment-based function, please check whether your bootstrap file has been uploaded successfully and ensure that the invocation path is correct.
Please check whether all the files in the code package or container image are required files. Appropriate streamlining can improve the initialization speed of the container.
Please check whether there are any exceptions or time-consuming business logic in the initialization code. You can appropriately increase the initialization timeout period and try again.
447
PullImageTimeOut
Image pull times out.
It may be a timeout caused by a large image or network jitters. Minimize the image or increase the initialization timeout period and try again. If the problem persists, submit a ticket.
449
InsufficientResources
There are no resources available at the resource specification selected by this function in the specified region.
If the resource type is high-spec CPU or GPU, it can be used with the provisioned concurrency. If the problem persists, submit a ticket.
450
InitContainerTimeout
Container start times out.
The container start duration exceeds the initialization timeout period. Minimize the code or increase the initialization timeout period and try again.
499
RequestCanceled
The function execution request is canceled.
For an asynchronously executed function, if the user cancels the function execution request, this message will be returned.
For an HTTP-triggered function, if the timeout period of an API Gateway trigger is less than the sum of the initialization duration and execution duration of the function, this message will be returned. Please check whether there is any exceptionally time-consuming business logic in the code or increase the backend timeout period of the API and try again.
500
InternalError
Internal error
An internal error occurs. Try again later. If the problem persists, submit a ticket.
Concepts
Execution method
The execution method specifies which function in which file is executed first when the cloud function is invoked.
For Go programming, use the FileName format, such as main.
For Python, Node.js, or PHP programming, use the FileName.FunctionName format, such as index.main_handler.
Note that FileName does not include the file name extension, and FunctionName is the name of the entry function. Ensure that the file name extension matches the programming language. For example, for Python programming, the file name extension is .py, and for Node.js programming, the file name extension is .js. For more information, see "Execution Method" in Basic Concepts.
For Java programming, use the package.class::method format, such as example.Hello::mainHandler.
For custom runtime, you can ignore the above patterns, and write the execution method in your custom language.
Yes
No
Was this page helpful?