Workflows
Create, version, deploy, and run AI workflows in Floprints. Lifecycle from composing through ready, with immutable version history.
Blueprint lifecycle
A blueprint (workflow) moves through these statuses:
| Status | Meaning |
|---|---|
composing | Active composer session; plan still being designed |
draft | Plan saved but not yet deployed |
deploying | Harnesses being created or reconciled |
ready | Deployed version available for runs |
failed | Deploy or compose failed |
Versions
Every compose or redeploy creates an immutable workflow_version containing:
- Full WorkflowPlan
- Model used by the composer
- Tools snapshot
- System-prompt hash
- Edit summary
- Complete composer transcript
Version lifecycle: draft → deploying → deployed → superseded (or failed).
A blueprint tracks currentVersionId and deployedVersionId independently — enabling rollback and side-by-side history.
Console surfaces
| Page | Purpose |
|---|---|
| Workflows list | All blueprints with status and last activity |
| Compose | Conversational design session |
| Detail | Plan view, version history, deploy controls |
| Run | Execute and chat with a deployed workflow |
| Run detail | Step trace, messages, token usage, human requests |
Runs
Each execution creates a run with:
- Status:
pending,running,completed,failed,timed_out - Phase: adds
waiting_humanwhen paused for input - Per-agent steps with input/output and timing
- Full message trace (roles, content, stop reason, token usage, latency, reasoning)
- Human requests when the workflow asks a question
Orchestrator runs can be continued via follow-up turns that append to the persistent session.
Background poller
A 5-second background worker resumes runs left in running or waiting_human: applies human answers, performs crash-recovery re-invocation, and guards against double-invocation.