Skip to content

Commit ed07a22

Browse files
committed
docs(srv): add faq entry on cron MTA-5983
1 parent e3282fc commit ed07a22

File tree

2 files changed

+21
-1
lines changed

2 files changed

+21
-1
lines changed

pages/serverless-containers/faq.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -189,6 +189,16 @@ Serverless Containers namespaces and Container Registry namespaces observe the f
189189

190190
- 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.
191191

192+
### How can I call my containers periodically?
193+
194+
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.
195+
196+
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.
197+
198+
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.
199+
200+
To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-containers/reference-content/cron-schedules/).
201+
192202
### How do Serverless Containers health checks work ?
193203

194204
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).

pages/serverless-functions/faq.mdx

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,17 @@ In the `Serverless Functions Logs` dashboard, you will then be able to read info
213213

214214
### How can I test my functions locally?
215215

216-
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.
216+
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.
217+
218+
### How can I call my functions periodically?
219+
220+
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.
221+
222+
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.
223+
224+
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.
225+
226+
To learn more on how CRONs work, refer to our [CRON schedule reference documentation](/serverless-functions/reference-content/cron-schedules/).
217227

218228
### Where can I find some advanced code examples for functions?
219229

0 commit comments

Comments
 (0)