From ed07a220e5edf380e8d112094a84612579db9381 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Tue, 29 Apr 2025 12:07:41 +0200 Subject: [PATCH 1/2] docs(srv): add faq entry on cron MTA-5983 --- pages/serverless-containers/faq.mdx | 10 ++++++++++ pages/serverless-functions/faq.mdx | 12 +++++++++++- 2 files changed, 21 insertions(+), 1 deletion(-) diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index ff573ee645..ed17f055b0 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -189,6 +189,16 @@ Serverless Containers namespaces and Container Registry namespaces observe the f - If you delete the Container Registry namespace associated with a Serverless Containers namespace, it will be created again when deploying a container within this Serverless Containers namespace. + ### How can I call my containers periodically? + + Scaleway Serverless Containers natively support CRON triggers to call your containers periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. + + Periodic CRON triggers also alow you to maintain your containers active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. + + Refer to the [dedicated documentation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to create CRON triggers for your containers. + + To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/). + ### How do Serverless Containers health checks work ? A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it is important to run them before binding to the port (starting the webserver). diff --git a/pages/serverless-functions/faq.mdx b/pages/serverless-functions/faq.mdx index a0fa36c508..7eed8e9a86 100644 --- a/pages/serverless-functions/faq.mdx +++ b/pages/serverless-functions/faq.mdx @@ -213,7 +213,17 @@ In the `Serverless Functions Logs` dashboard, you will then be able to read info ### How can I test my functions locally? - Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information. +Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information. + +### How can I call my functions periodically? + +Scaleway Serverless Functions natively support CRON triggers to call your functions periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. + +Periodic CRON triggers also alow you to maintain your functions active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. + +Refer to the [dedicated documentation](/serverless-functions/how-to/add-trigger-to-a-function/) for more information on how to create CRON triggers for your functions. + +To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/). ### Where can I find some advanced code examples for functions? From f0eaf25d39a05e238ab73dad67d2723f090c9879 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 30 Apr 2025 16:24:59 +0200 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- pages/serverless-containers/faq.mdx | 4 ++-- pages/serverless-functions/faq.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pages/serverless-containers/faq.mdx b/pages/serverless-containers/faq.mdx index ed17f055b0..8b8a32811a 100644 --- a/pages/serverless-containers/faq.mdx +++ b/pages/serverless-containers/faq.mdx @@ -193,11 +193,11 @@ Serverless Containers namespaces and Container Registry namespaces observe the f Scaleway Serverless Containers natively support CRON triggers to call your containers periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. - Periodic CRON triggers also alow you to maintain your containers active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. + Periodic CRON triggers also allow you to maintain your containers active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. Refer to the [dedicated documentation](/serverless-containers/how-to/add-trigger-to-a-container/) for more information on how to create CRON triggers for your containers. - To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/). + To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/). ### How do Serverless Containers health checks work ? diff --git a/pages/serverless-functions/faq.mdx b/pages/serverless-functions/faq.mdx index 7eed8e9a86..614596c689 100644 --- a/pages/serverless-functions/faq.mdx +++ b/pages/serverless-functions/faq.mdx @@ -219,11 +219,11 @@ Scaleway provides libraries to run your functions locally, for debugging, profil Scaleway Serverless Functions natively support CRON triggers to call your functions periodically. This feature has many applications, such as scheduled data processing, maintenance tasks, monitoring, or reporting. -Periodic CRON triggers also alow you to maintain your functions active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. +Periodic CRON triggers also allow you to maintain your functions active during specific time slots to reduce cold start latency, without having to provision a minimum of 1 vCPU at all times. Refer to the [dedicated documentation](/serverless-functions/how-to/add-trigger-to-a-function/) for more information on how to create CRON triggers for your functions. -To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/). +To learn more about how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/). ### Where can I find some advanced code examples for functions?