Flow Schedules

Cloud Integration shows a schedule only inside the flow it belongs to. This tool shows every schedule of the tenant together: as a list, as a day and as a week.

When to use it

• Before you add a nightly job: what else runs at 02:00, and where do many flows start in the same minute?
• To find the quiet hours for a maintenance window.
• To see which schedules are externalised, under which parameter, and which externalised schedule has no value.

What it shows

• Timer start events and polling sender adapters such as SFTP and mail. They run on the same scheduler and load the same systems.
• Each schedule in words, with its next runs in your own time zone or UTC, whatever zone the schedule was set in. 08:00 Europe/Berlin stays 08:00 there across clock changes.
• Whether the flow is deployed, and whether what runs is the design-time version.

Schedules that run more often than every 15 minutes are drawn as a band over their active hours, so they do not drown everything else.

How it works

Schedules are read from the flows recorded by the artifact sync. Nothing is read from the tenant when you open the page.

Good to know

• It shows when a flow would start, not whether it ran. For that, see Message Logs.
• It shows design time. A schedule configured at deployment and changed in design time since is shown as design time has it; the list marks flows whose deployed version differs.
• Cron expressions with L, W or # (last day of the month, nearest weekday, third Friday) are listed with their expression but not drawn in the day and week views.
• Start and end dates of an advanced schedule are not read.
• “Run once” schedules are listed but have no place on a calendar.