maestro
latest
false
Maestro user guide
- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Start a workflow automatically on a recurring schedule using intervals or cron expressions.
Starts the workflow automatically on a recurring schedule. Use this trigger for periodic automation tasks such as daily reports, hourly data synchronization, or weekly cleanup jobs.
Configuration
| Field | Required | Description |
|---|---|---|
| Schedule type | Yes | How the schedule is defined: Interval (every N minutes/hours/days) or Cron (a cron expression for precise scheduling). |
| Interval | Conditional | The repeat interval and unit (minutes, hours, or days). Required when schedule type is Interval. |
| Cron expression | Conditional | A standard cron expression (5 fields). Required when schedule type is Cron. |
| Time zone | Yes | The time zone used to interpret the schedule. Default: UTC. |
| Input schema | No | Static input variable values to pass to the workflow on each scheduled run. |
Examples
| Goal | Schedule type | Value |
|---|---|---|
| Every 30 minutes | Interval | 30 minutes |
| Every day at 9:00 AM | Cron | 0 9 * * * |
| Every Monday at midnight | Cron | 0 0 * * 1 |
| Every hour | Interval | 1 hour |
Notes
- If a workflow is still running when its next scheduled start time arrives, the new run is skipped or queued depending on the Concurrency setting in the workflow's publish configuration.
- The Scheduled Trigger does not fire until the flow is published.