Skip to main content

Frequently Asked Questions FAQ

Product Roadmap​

After currently providing Function Cloud Hosting, how will Cloud Functions or Cloud Functions 1.0 be handled subsequently? Will Cloud Functions 1.0 be discontinued?​

Function Cloud Hosting provides a set of runtime mechanisms different from Cloud Functions, each with distinct characteristics in user experience and operational performance. Both product capabilities will coexist long-term, and Cloud Functions will not be discontinued due to the provision of Function Cloud Hosting.

Why does it prompt that Cloud Hosting has been activated?​

Function Cloud Hosting utilizes the new version architecture of Cloud Hosting at its core. If your Cloud Development Environment has previously enabled Cloud Hosting services through the Tencent Cloud console, it will have activated the old architecture version, resulting in the inability to enable the new architecture Cloud Hosting service again.

You can access via: Tencent Cloud console - Cloud Development - the old version console in the upper right corner, enter the old version console, and via the Cloud Hosting in the left sidebar, access the old architecture Cloud Hosting service.

You can delete all services in the old architecture Cloud Hosting to clean up and discontinue using the old architecture. After cleanup is complete, subsequently enable the new version Cloud Hosting and Function Cloud Hosting through the development platform portal.

If you have further questions or are unsure how to proceed, you can seek assistance by submitting a ticket.

How Function Cloud Hosting is Billed​

Currently, Function Cloud Hosting operates using the Cloud Hosting instance model, with billing based on instance specifications and runtime. The billing items for using Function Cloud Hosting include:

  • Core-hour: After an instance is started, each core used by the instance running for one hour is billed as 1 core-hour; for example: one instance with 1 core running for one hour is billed as 1 core*hour;
  • GB-hour: After an instance is started, the memory used by the instance running for one hour is billed as one GB-hour; for example: one instance with 2GB memory running for one hour is billed as 2 GB*hours;
  • Number of invocations: Calls to Function Cloud Hosting via the callContainer method from Mini Program or web clients will be counted as invocations and billed together with the overall Cloud Hosting package; Calls initiated through the public network address provided by Function Cloud Hosting will not be counted as invocations
  • Outbound traffic: Traffic flowing out from the function instance is counted as outbound traffic; for example, uploading files externally from within the function or request packets from initiating requests are all outbound traffic; downloading files within the function or response packets from requests are inbound traffic and not billed;

Why is it necessary to enable over-limit pay-as-you-go for the Cloud Development environment when using Function Cloud Hosting​

Currently, the billing items for Function Cloud Hosting are not included in the Cloud Development package; instead, they are charged through pay-as-you-go billing. The pay-as-you-go billing items can only be properly activated after enabling over-limit pay-as-you-go for the Cloud Development environment. Function Cloud Hosting services can only start and run normally after the billing items are properly activated, which requires enabling over-limit pay-as-you-go in the Cloud Development environment where the function resides.