Skip to content

Commit eb0f10d

Browse files
docs(srv): add doc on cron schedules MTA-4231 (#2799)
* docs(srv): add doc on cron schedules MTA-4231 * docs(srv): update * docs(srv): update
1 parent 742d3f2 commit eb0f10d

File tree

7 files changed

+48
-5
lines changed

7 files changed

+48
-5
lines changed

macros/serverless/cron-schedules.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,4 +62,10 @@ Several operators can be added to each field to further refine your schedule.
6262
| `0 9 1-24 DEC *` | Runs at 9:00 every day during the first 24 days of December |
6363
| `30 17 * * 5` | Runs at 17:30 every Friday |
6464
| `0 0 * 8 *` | Runs at 00:00 (midnight) every day in August |
65-
| `1 1 1 1 1` | Runs every January 1st, at 01:01 and on Mondays in January |
65+
| `1 1 1 1 1` | Runs every January 1st, at 01:01 and on Mondays in January |
66+
67+
## Time zones
68+
69+
- Serverless Functions and Serverless Containers [CRON triggers](/serverless/functions/concepts#cron-trigger) use the **UTC** time zone. This parameter cannot be modified.
70+
71+
- Serverless Jobs allow modifying the time zone of their schedules via the Job **Settings** tab. Refer to [the job scheduling documentation](/serverless/jobs/how-to/manage-job-schedule/) for more information.

menu/navigation.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1358,6 +1358,10 @@
13581358
"label": "Monitor a job",
13591359
"slug": "monitor-job"
13601360
},
1361+
{
1362+
"label": "Manage the scheduling of a job",
1363+
"slug": "manage-job-schedule"
1364+
},
13611365
{
13621366
"label": "Delete a job",
13631367
"slug": "delete-job"

serverless/containers/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Container Registry is the place where your images are stored before being deploy
2828

2929
## CRON trigger
3030

31-
A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format. Refer to our [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information.
31+
A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information.
3232

3333
## GB-s
3434

serverless/containers/how-to/add-trigger-to-a-container.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ NATS subjects of the [Scaleway Messaging and Queuing](/serverless/messaging/quic
7373

7474
## CRON triggers
7575

76-
A CRON trigger is a mechanism for invoking a Serverless Container at a specific time or on a recurring schedule, similar to a traditional cron job on a Linux server.
76+
[CRON triggers](/serverless/containers/concepts/#cron-trigger) allow you to invoke your containers based on a recurring schedule. The CRON triggers for Serverless Containers use the **UTC** time zone.
7777

7878
1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays.
7979
2. Click the relevant containers namespace.

serverless/functions/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Cold start is the time a function Instance takes to handle a request when it is
1616

1717
## CRON trigger
1818

19-
A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format. Refer to our [cron schedules reference](/serverless/functions/reference-content/cron-schedules/) for more information.
19+
A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/functions/reference-content/cron-schedules/) for more information.
2020

2121
## Environment variables
2222

serverless/functions/how-to/add-trigger-to-a-function.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ NATS subjects of the [Scaleway Messaging and Queuing](/serverless/messaging/quic
6565

6666
## CRON triggers
6767

68-
[CRON triggers](/serverless/functions/concepts/#cron-trigger) allow you to invoke your functions based on a recurring schedule.
68+
[CRON triggers](/serverless/functions/concepts/#cron-trigger) allow you to invoke your functions based on a recurring schedule. The CRON triggers for Serverless Functions use the **UTC** time zone.
6969

7070
1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays.
7171
2. Click the relevant functions namespace.
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
meta:
3+
title: How to manage the scheduling of a Serverless Job
4+
description: This page explains how to manage the scheduling parameters of a Serverless Job
5+
content:
6+
h1: How to manage the scheduling of a Serverless Job
7+
paragraph: This page explains how to manage the scheduling parameters of a Serverless Job
8+
dates:
9+
validation: 2024-02-27
10+
posted: 2024-02-27
11+
categories:
12+
- serverless
13+
- jobs
14+
---
15+
16+
Job scheduling allows you to execute a Serverless Job on a recurring schedule, based on a [cron expression](/serveress/jobs/reference-content/cron-schedules), in the `* * * * *` format, using the desired time zone.
17+
18+
<Macro id="iam-requirements" />
19+
20+
<Message type="requirement">
21+
- You have an account and are logged into the [Scaleway console](https://console.scaleway.com)
22+
- You have [created a Serverless Job](/serverless/jobs/how-to/create-job-from-scaleway-registry/)
23+
</Message>
24+
25+
1. Click **Jobs** in the **Serverless** section of the side menu. The jobs page displays.
26+
27+
2. Click the name of the job you want to manage, then click the **Settings** tab.
28+
29+
3. Scroll down to the **Job scheduling** section, and edit the cron expression and the time zone.
30+
31+
<Message type="note">
32+
Refer to the [dedicated documentation](/serveress/jobs/reference-content/cron-schedules) for more information on cron scheduling and time zones.
33+
</Message>

0 commit comments

Comments
 (0)