Skip to main content

Cloud Function Related

How to resolve cloud function execution timeout?​

When a timeout occurs, the client will directly disconnect and report an error. It is recommended to control the function execution time and avoid placing time-consuming operations in cloud functions directly invoked by the client.

How to use the built-in modules in cloud functions?​

  • Cloud function built-in modules are already integrated into the runtime environment and can be used directly.
  • If the built-in module versions cannot meet the requirements, you can install modules yourself into the cloud function, and they will be prioritized by default.

? Currently supported built-in modules are request 2.87.1.

How to handle long-running operations in cloud functions?​

To ensure a good client experience, direct invocation of time-consuming cloud functions is not allowed.

  • It is recommended to adjust the required timeout (up to 60s) in the cloud console. Use callback() in the cloud function to return success, allowing the client to proceed without waiting for execution results.
  • Cloud functions will continue executing within the timeout period until completion or timeout, write the execution results to storage services such as databases, and then retrieve the result on the client side.

Why is exit status 11 returned when updating the cloud function?​

Please check the function's packaging method and entry method.

  • When creating a cloud function, the default execution method is index.main, where the entry file is index.js, and index.js must expose the main method using export.
  • When updating a cloud function, if you choose to upload via a zip package, pay attention to the packaging method: ensure the first-level content after unzipping must include the entry file (a common packaging mistake is placing function code in a subfolder and compressing that folder, resulting in unzipped content being a folder without the entry file index.js).

Are some logs missing during cloud function testing?​

  • During cloud function testing, when using synchronous invocation (timeout less than 20 seconds), the returned logs are limited to 4k, and logs exceeding 4k are not displayed.
  • For asynchronous invocation (timeout greater than or equal to 20 seconds), the returned logs are limited to 6M, and logs exceeding 6M are not displayed.

How to Invoke a Cloud Function from Another Cloud Function​

Currently, it can only be invoked through the SDK provided by Cloud Development, with no other methods available.

Sharing Code Files (Directories) Between Different Cloud Functions​

Not launched

Does Node.js Cloud Function Support Both Asynchronous and Synchronous Writing Patterns?​

Yes, it is recommended to use the synchronous (async/await) writing approach.

How to Store Secret Keys and Configuration Information Within Cloud Functions​

Cloud Functions are stateless; it is recommended to store configuration information in the Cloud Development database service.