Scheduled Jobs
Automate recurring operational work with configured schedules, reusable programs, and visible execution history.
Define what runs, when it runs, and whether it repeats. Connect schedules to programs that create work, update records, check conditions, trigger notifications, or synchronize data.
Explore the CapabilityScheduled Jobs
Flexible Schedule Configuration
- Create schedules with a name, description, active status, start date and time, and recurrence behavior.
- Support one-time, daily, weekly, monthly, interval-based, or cron-style execution patterns.
- Pause, revise, or retire schedules without changing the underlying business program.
In practice
Control automation during maintenance
An administrator deactivates or adjusts a schedule during maintenance while preserving its program configuration. Timing changes independently of business logic.
Scheduled Jobs
Program-Based Execution
- Attach schedules to programs containing the business logic to execute.
- Generate tasks, check overdue records, update attributes, calculate metrics, synchronize data, or perform clean-up.
- Reuse a program across schedules, locations, business units, or timing rules.
In practice
Daily work preparation
A recurring daily schedule runs a task-generation program so planned jobs are ready for dispatchers, technicians, inspectors, or operators at the expected time.
Scheduled Jobs
Run Tracking and Monitoring
- Generate run instances with planned run time, requested start, projected date, execution status, and history.
- Review completed, pending, in-progress, and failed runs for support and audit visibility.
- Use history to diagnose failed automation, missed execution windows, and incorrect recurrence behavior.
In practice
Confirm automation executed
Support and audit teams review generated run instances and history to establish when a scheduled program ran and whether it completed successfully.
Scheduled Jobs
Governed and Condition-Based Automation
- Restrict who can create, activate, edit, or disable schedules.
- Evaluate conditions before taking action, such as overdue work, incomplete forms, or failed integration responses.
- Connect results to notifications, lifecycle commands, dashboards, and integrations.
In practice
Monitor approaching SLA breaches
A scheduled program checks open records approaching an SLA breach and marks or escalates them. Responsible users receive alerts when configured conditions require attention.
How Scheduled Jobs Works
Define the objective: create work, check status, update data, calculate metrics, notify users, or synchronize systems.
Configure the start time, active flag, recurrence pattern, and frequency.
Select or configure the program containing the business logic.
Validate generated run instances and expected execution windows.
Connect outcomes to notifications, lifecycle changes, reports, or external integrations.
Monitor run history and failures to refine timing or program logic.
Connected and Governed
- Check lifecycle states to trigger reminders, escalations, status updates, or automated transitions.
- Send notifications from scheduled programs when configured conditions are met.
- Monitor Dynamic Forms for incomplete responses, pending reviews, or overdue corrective actions.
- Synchronize external APIs, OData, ERP, PLM, service, reporting, and document systems through scheduled integration programs.
Business Value
- Automate repetitive, time-based operational work.
- Improve reliability with visible run instances and execution history.
- Manage timing independently from business logic.
- Support proactive operations by connecting schedules, programs, workflows, and notifications.
Run Recurring Work with Visibility and Control
Configure schedules around operational needs, reuse business programs, and track the execution of background work across your processes.