Comment on page
Create and manage time-based service triggers for workflow automation.
Schedules are used to automate services and run them at set times. Common use cases are running batch and recurring jobs such as synchronizing data with an external system, polling for changes, and sending notifications.
Any task that needs to be run on a regular schedule is a candidate for a schedule.
- Fetch data from an external API every 15 minutes to populate a dashboard.
- Synchronize customer data with your CRM nightly at 2am.
- Refresh an OAuth access token used for integrations every 3 hours.
- Send an email every morning with a summary of all orders from the previous day.
- Ensure that the selected service account has permission to run the selected service and the necessary object class permissions. If you are updating a secret within the service, that permission must be granted.
- After you have enabled a service you will need to disable it to make changes. Don't forget to enable it again when you're done!
A cron expression typically consists of five values separated by spaces, in this order, within the stated ranges.
- Minute (0–59)
- Hour (0–23)
- Day of month (1–31)
- Month (1–12)
- Day of week (0–6, where 0 = Sunday)
The following example would be run every 3rd hour, on the hour:
0 */3 * * *.
Schedules also support second granularity (0–59). This can be added as the first value in the expression if required.