Scheduling flows

Scheduling basics

In Integrator, you can schedule flows for automatic execution.

To schedule a flow, open the Scheduler window

...and click the Schedule button:

In this window you can also:

• Filter scheduled flows (events) by name and type.
• Select events for group operations.
• Disable events. Disabled events will not be automatically executed by the scheduler.
• See flow statistics.
• Manually execute selected flows.
• Edit events (change scheduling parameters).

Scheduling periodically executed flows

Flows can be scheduled to be executed automatically at configurable time intervals. A scheduled flow is called an Event.

When scheduling events, the following parameters are available:

• Name - the name of the event.
• Flow - the flow associated with the event.
• Schedule - a cron-based or seconds-based time when the flow should be executed.
• Active - inactive flows will not be executed automatically.
• Send email on success - if enabled, the Scheduler will notify an Emails subscription list about each successful execution of the flow.
• Send email on failure - if enabled the Scheduler will notify an Emails subscription list about each failed execution of the flow.
• Emails - a space-separated list of email addresses that will be notified about success or failure.
• Retry on failure - if enabled and execution has failed, the Scheduler will retry the flow for the configured number of retries.
• Retries - the number of retries for failed execution attempts.
• Delay between retries - the delay between retries, in minutes.
• Record Console Log - if enabled, the DEBUG level log will be recorded for each flow execution. This options is enabled by default for the scheduled periodically executed flows.
• Extra Log Step - an extra checkpoint which will be added to the flow log every time the specified number of data records has been processed. While expanding the verbosity of the log, it can also negatively impact performance. Use Extra Log Step if you want to monitor a flow which is processing a large number of data records, typically > 1M(one million). Otherwise, keep it empty.
• Keep Empty Statistics - keep flow execution statistics even in case of successful execution with 0 records, or files. By default, this option is enabled.

Examples of scheduling, using the cron pattern

Every day, every 4 hours

1. Select time period
2. Select Every day
3. Select 0, 8, 8, 12, 16, 20, 23 for hours and 0 for minutes

Every Monday, Wednesday and Friday at 23:59

1. Select time period
2. Select Every week
3. Select Monday, Wednesday and Friday for days and 23:59 for hours and minutes

Every day at 1:00 am

1. Select time period
2. Select Month
3. Select Every day of the month
4. Select 1:00 for hours and minutes

Every 20 minutes

1. Select time period
2. Select Every hour
3. Select 0,20,40,59

Scheduling real-time flows

Flows can be scheduled to be executed in real-time.

real-time scheduling is only available for Enterprise and on-premise plans.

if real-time flow fails it will be automatically deactivated. The user will need to reactivate the flow manually.

to pause/resume the real-time flow simply select it and toggle the Activate/Deactivate button.

When scheduling real-time events, the following parameters are available:

• Name - the name of the event.
• Flow - the flow associated with the event.
• Schedule - select Real-time.
• Active - inactive flows will not be executed automatically.
• Send email on failure - if enabled the Scheduler will notify an Emails subscription list about each failed execution of the flow.
• Emails - a space-separated list of email addresses that will be notified about success or failure.
• Keep Empty Statistics - keep flow execution statistics even in case of successful execution with 0 records, or files. By default, this option is disabled.

Scheduling event-driven flows

When scheduled, event-driven flows are executed "on event", which typically means when the payload arrives. For example, when a third-party application calls Integrator's HTTP endpoint, which is linked to an HTTP listener.

When scheduling event-driven flows, the following parameters are available:

• Name - the name of the event.
• Flow - the flow associated with the event.
• Active - inactive flows will not be executed automatically.
• Send email on success - if enabled, the Scheduler will notify the Emails subscription list about each successful execution of the flow.
• Send email on failure - if enabled, the Scheduler will notify the Emails subscription list about each failed execution of the flow.
• Emails - a space-separated list of email addresses to be notified about success or failure.
• Retry on failure - if enabled and execution has failed, the Scheduler will retry the flow for the configured number of retries.
• Retries - the number of retries for failed execution attempts.
• Delay between retries - the delay between retries, in minutes.
• Record Console Log - if enabled, the DEBUG level log will be recorded for each flow execution. This options is disabled by default for the scheduled event-driven flows.
• Extra Log Step - an extra checkpoint which will be added to the flow log every time the specified number of data records is processed. While expanding the verbosity of the log, it can also negatively impact performance. Use Extra Log Step if you want to monitor a flow which is processing a large number of the data records, typically > 1M(one million). Otherwise, keep it empty.
• Keep Message - if enabled, system will store bodies of the POST/PUT requests in the database. The stored messages can be viewed in the messages app. The option is disabled by default.
• Keep Empty Statistics - keep flow execution statistics even in case of successful execution with 0 records, or files. By default, this option is enabled.

after an event-driven flow has been scheduled, you will need to wait one minute before you can start using it. The reason: Listeners need to be activated, which usually takes ~ 1 minute.