Scheduled flows

This documentation describes the options for defining the flow schedule.

A flow can be configured to run automatically according to a schedule defined in the flow settings. The options for defining the schedule are as follows:
  • Time Interval/Unit – Two required properties that determine how much time should elapse after the flow runs before running it again. The unit determines if the interval is in terms of seconds, minutes, or hours and the time interval is a number. For example, having unit set to “seconds” and the time interval as 30 would result in the flow being run every 30 seconds.
  • End date – Specifies the date at which the flow should stop being run. If the current date is past the defined end date, the flow will no longer run automatically.
  • Select Days – Determines on which days the flow should run. By default, all days are selected so that the flow will run every day.
  • Start Time – Specifies the time each day when the flow should first start running. For example, if set to 15:00, the flow will be scheduled to begin running every day at 3PM. Must be set together with End Time. If start time is not specified, the flow will begin running as soon as it is deployed as long as the current day is within the selected days.
  • End Time – Specifies he time each day when the flow should stop running. For example, if it is set to 20:00, the flow will not run automatically any time after 8PM. Must be set together with Start Time.
  • Time Zone – Specifies the time zone to be used to determine when the flow should be run. If not specified, the time zone of the machine where the REST Runtime is running will be used.
  • Skip If Busy – If enabled, the option allows only one instance of the flow to run at once so that if one run of the flow takes longer than the time interval defined, another instance will not run until the next time that the flow would have been scheduled to run.