Overview
The Schedules page (Runtime → Runtime Settings → Schedules) lists the Timer Start Events that start process instances and the workflow schedules that start workflow runs. You can view them and activate or deactivate them without a redeployment. This feature is especially useful in upper environments, where you might need to pause or resume cron jobs without modifying the project build.Timer Start Event
Check this section for more details about Timer Start Events and how to configure them.

Where are workflow schedules managed?
This page is called Schedules (Runtime → Runtime Settings → Schedules). It lists process timers and workflow schedules together, and the Origin filter (Process or Workflow) separates them. You activate and deactivate workflow schedules here the same way as process timers.Key components
1. List of schedules
The Schedules page displays every process timer and workflow schedule. Each row in the list shows:- State: Whether the schedule is active.
- Origin: Process for a Timer Start Event, Workflow for a workflow schedule.
- Name: The process or workflow the schedule starts.
- Schedule: The name of the timer node or of the workflow schedule.
- Type:
- Date: Triggers at a specific date and time.
- Cycle: Repeats at defined intervals (for example, every 10 seconds).
- Location: Local, or the name of the dependency the schedule comes from.
2. Schedule details
To view a schedule’s configuration, click the View icon next to it in the list. The Schedule details dialog shows the process or workflow, the swimlane of a process timer, the schedule name, the location, the expression, and the next fire times.
3. Activating and deactivating schedules
Manage timer activation directly from the UI:
- Activate: Click the Activate button on the schedule’s row, then confirm. The confirmation lists the next fire times and warns you when the schedule has none.
- Deactivate: Click the same button, now Deactivate, and confirm to suspend the schedule.
Use cases
1
Employee Onboarding reminder
A Timer Start Event can be scheduled to automatically trigger an onboarding process at a predefined time.Example: Process starts on January 28, 2025, at 12:14 PM, sending onboarding notifications.
2
Recurring Data processing jobs
A Cycle timer can execute a job every 10 seconds for 60 repetitions, ensuring periodic execution.
3
Scheduled Report generation
A cycle timer with a cron expression can generate a report at 1 AM every day.
Additional notes
-
Runtime Timer Control:
Manage timers in the Runtime tab without changing the application build. The Timer Start Event node itself has no activation setting. -
Timers in Multi-Swimlane Processes:
Each swimlane can have its own timer. The Schedules page displays each timer separately for clear management. -
Exporting and Importing Builds:
Timer activation settings are not editable during build export/import. All timer management occurs in the Runtime tab.
Related resources
Timer Start Event
Configure the Date or Cycle timer that schedules a process
Timer expressions
ISO 8601 and cron syntax for timer definitions
Active policy
Choose the build whose timers are scheduled

