Skip to main content

Workflows

A Workflow is a durable business execution flow that can wait, resume, retry, escalate, and continue while preserving context and supervision.

What this means​

In Subbasis, a workflow is not just an automation trigger. It is a governed execution model that survives real-world timelines and interruptions.

Why it matters​

Business operations often run over hours, days, weeks, or months. A trigger-only approach cannot reliably preserve state, approvals, and evidence across that span.

Durable workflow principles include:

  • wait / resume behavior
  • retry and escalation paths
  • explicit human approval gates
  • context and state preservation
  • evidence continuity

How Subbasis handles it​

Subbasis distinguishes key runtime entities:

  • Workflow definition: reusable process blueprint.
  • Workflow execution: one live run instance.
  • Workflow step: one transition or unit of process logic.
  • Agent task: work assigned to an agent role.
  • Approval gate: required decision checkpoint before action.
  • Connector action: governed operation on external/internal systems.
  • Evidence event: execution-grade record of meaningful action or decision.

Example scenarios​

Client onboarding​

New client signs contract, then onboarding execution tracks data collection, approvals, system setup, and kickoff readiness across multiple teams.

Support escalation​

Initial support triage is automated, but severe incidents trigger approval-driven escalation and role handoff with preserved context.

Sales prospect follow-up​

Agent proposes outreach, approval gate validates policy, connector executes CRM/message update, evidence logs outcome.

Finance approval workflow​

Agent prepares vendor payment request, but external payment action only proceeds after explicit human approval.

What to configure​

  • workflow definitions and transition logic
  • agent role assignment per step
  • approval gate conditions and escalation owners
  • connector bindings and allowed operations
  • retries/timeouts/resume conditions
  • evidence and context requirements by step

Limits and deployment notes​

  • Subbasis is designed around durable execution principles.
  • Do not assume infinite execution duration or certification claims.
  • Execution characteristics depend on plan and deployment topology.