- 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
Deploying a Flow makes it available to run in production. Before you deploy, you build and test your flow in the canvas — running it in Debug and checking it with Eval — but it cannot be triggered by external events, run on a schedule, or invoked by other systems until it is deployed.
How deployment works
When you deploy a Flow, the platform:
- Validates the workflow definition (checks for missing required fields, broken connections, and unresolved variables). Blocking validation errors stop the publish — you must resolve them before you can deploy.
- Packages the workflow.
- Publishes the package to Orchestrator and activates any triggers defined in the workflow (scheduled triggers start firing, integration triggers start listening).
Publishing a workflow
- Open the workflow on the canvas.
- Select Publish in the top toolbar.
- Confirm.
Result
The workflow is published to Orchestrator and activated. Any triggers defined in the workflow become active — scheduled triggers start firing and integration triggers start listening.
If validation finds blocking errors, the publish is stopped and the errors are reported. Resolve them and publish again.
Deploying from the editor
You can also publish by packaging your workspace and deploying it to Orchestrator from the editor. The editor uploads the workflow to Studio Web as part of this path. Refer to Flow in VS Code for packaging and deploying from a local workspace.
Common mistakes
- Publishing without testing — Always run your flow in Debug at least once before publishing.
- Ignoring validation errors — Blocking validation errors stop the publish. Resolve every reported error before you deploy.