Schedules

The Schedules node allows you to create and edit schedules that will automatically start an instance of a workflow at a particular date in the future, or some type of recurring pattern (e.g. once a week). For example, you may have an Audit workflow that needs to start automatically once a month. Setting up a schedule for this workflow to start automatically means that you do not have to remember to start the workflow manually each month.

From the Schedules node, you can Add, Save, Edit, Delete or Refresh Workflow Schedules.

Field Name Description
New Click New to create a new Schedule.
Save Click Save to save all Schedules.
Edit Click Edit to edit a Schedule.
Delete Click Delete to remove a Schedule.
Refresh Click Refresh to refresh the list of Schedules.
Workflow Displays the workflow associated to the Schedule.
If the workflow associated to the Schedule fails, errors will surface in the Errors section of the Workflow Server node and Errors tab in the Process Details page of the workflow.
Name Displays the name of the Schedule.
Description Displays the description of the Schedule.
Recurrence Displays the recurrence of the Schedule, such as once, daily, weekly, monthly, yearly and interval.
Last Run Date Displays the last date and time the Schedule was run. This field is timezone aware and adjusts according to the timezone your browser is using.
Success Displays a count of how many times the Schedule ran successfully.
Failed Displays a count of how many times the Schedule failed.
Enabled Enables the Schedule. When selecting the Enabled check box. The user account who created the Schedule is used to start the Schedule.
When you create a Schedule, you need start rights on the workflow in order for the workflow associated to the Schedule to start. You can create a custom user account to start schedules for you, ensure the custom user account has start rights on the associated workflow.
You must recreate a schedule when you deploy a new version of the workflow when item references or data fields are changed, otherwise, the schedule won't start the workflow as expected.