Build Workflows
Design workflows for durability, not only speed.
What this means
Building workflows in Subbasis means modeling operational reality, not only event automation.
Why it matters
Operations involve approvals, failure handling, role handoffs, and external systems. Durable workflow design reduces breakage and rework.
How Subbasis handles it
Workflow building usually includes:
- explicit step boundaries
- transition conditions
- approval checkpoints
- connector action boundaries
- evidence expectations per stage
- context continuity rules
Build checklist
- Define steps and transition conditions.
- Add approvals where risk changes.
- Add retries and escalation paths.
- Attach context and evidence requirements.
Example scenario
Finance operation:
- Step 1: collect request details.
- Step 2: validate policy constraints.
- Step 3: route to approval gate.
- Step 4: execute connector action if approved.
- Step 5: capture evidence and close.
What to configure
- timeouts, retry rules, and escalation owners
- role ownership by step
- approval policy mapping
- connector permissions
- evidence schema and retention expectations
Limits and deployment notes
- Workflow volume and complexity depend on plan/deployment.
- Long-running operations are supported by durable execution patterns, but implementation details should be validated for your environment.
Related docs
See Build agents and Connectors & ACC.