maestro
latest
false
- Introduction
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- 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)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process modeling with Flow
- Getting started
- Core concepts
- Node reference
- Build guides
- Best practices
- Reference
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
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.