The Scheduler is a persistent task that activates its transition at the times specified by its schedule.
The Scheduler activity should be considered as a scheduled start. The activity positioning rules within the chart are the same as for the Start activity. This activity must not have an inbound transition.
It is a best practice not to schedule a workflow to run more than every 15 minutes because it may impede overall system performance and create blocks in the database.
When building your workflow, never use more than one Scheduler activity per branch. For more on this, refer to: Using activities .
The scheduler defines the activation schedule of the transition. To configure it, double-click the graphical object, then click Change...
A wizard lets you define the frequency and validity period of the activity. The configuration steps are as follows:
- Select the activation frequency and click Next .
- Give the activation times and days. The parameters for this step depend on the frequency selected in the previous step. If you choose to launch the activity several times a day, the configuration options will be as follows:
- Define the validity period of the schedule, or specify how many times it will be executed.
- Check the configuration and click Finish to save.
Using a scheduler activity may lead to have several executions of a workflow running at the same time. For instance, you can have a scheduler triggering the workflow execution every hour, but sometimes the execution of the whole workflow takes more than an hour. You may want to skip the execution if the workflow is already running. For more on how to prevent simultaneous executions of a workflow, refer to this page .
Note also that the transition can be activated several hours later if the workflow was executing a long-term task, such as an import, or if the wfserver module was stopped for a time. In this case, it may be necessary to restrict the execution of the task activated by the scheduler to a certain time range.