Skip to content

Schedule

The cron job schedule determines when a cron job should start a new job instance. It is defined by a string of 5 elements as follows:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of the month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday)
│ │ │ │ │
* * * * *

Allowed values are also fractions like */5 to indicate for example every firth.

See Cron schedule syntax for more details.

The times are in UTC time.

Examples:

  • 0 * * * * runs every hour at 0 minutes.
  • 30 1 * * * runs every day at 1:30 AM
  • */10 * * * * runs every 10 minutes
  • 0 6 1 */2 * runs every two months on the first day of the month at 6:00 UTC

Long term authentication

In the jobs created from cronjobs, Platform SAS token is used for authentication and authorization to access to Platform resources. At the cronjob creation, an initial Platform SAS token is stored in the cronjob configuration. However, this token could expire. To prevent this token from expiring, Platform SAS tokens are refreshed evey day to update their validity several days into the future.

Listing existing scheduled jobs

It is possible to list scheduled jobs in a specific project, given that the user has at least read access to the project. As of September 2022 it is possble use the GET​/api​/process/project/{projectId}/cronjob/list endpoint for this.