Workflows: draft, publish, version
You edit a workflow as a draft. Publish turns the draft into a new, immutable version and makes it the version new runs use. Runs already in progress keep the version they started on, so publishing never changes a run mid-flight. You can test-run a draft before you publish it, and roll back by activating an earlier version. Publishing also checks what the version will act as: you must be allowed to use every agent the graph runs and every company Credential a step names. A publish you are not entitled to is refused and the draft is left untouched. A workflow you no longer need can be retired (it stops accepting runs) or deleted. Delete moves it to Trash, where it can be restored for 30 days; only Delete permanently removes it and its versions. You can build a workflow yourself in the graph builder, or ask the Workflow Architect to draft one from a description.Node types
Each step in the graph is a node. Forge Console labels the six node types as follows:
In the builder, an Agent node’s Assigned to field offers AI, Human and Role. When
the step is assigned to a person, the run waits for that person’s answer before it continues.
Runs
A run is pinned to the version it started on (or to the draft, for a test run). It records which steps ran, in what order, what each produced, what it cost, and the governance decisions made along the way. A run has one of six statuses:
A run starts in
running; there is no queued status. A run’s execution outcome is separate from its
status: it explains how execution ended, for example Completed normally or Completed with
handled error.
To try again after a run ends, rerun it with changed inputs or restart it from an eligible step.
Both create a new attempt; they do not resume the old one.
Triggers and schedules
A run starts in one of these ways:- Manually, from the workflow in Forge Console.
- From the API or MCP, by dispatching the workflow.
- On a schedule: a cron expression with a timezone, or a single one-shot time, set on the workflow’s Schedule tab. A schedule does not start a run while its workflow is paused, and a retired workflow accepts no new runs.
- From an inbound event, such as a call to the workflow’s ingress URL or an email route.
Human tasks
When a run reaches an Agent node whose worker is a person, or Trust Fabric holds an action for approval, Forge creates a human task and waits. It appears in the assignee’s My Work; the linked page lists every kind and how each is answered.Outcomes
Outcome has four meanings in Forge: how a run ended, how its execution got there, a work outcome that a completed run achieved, and a Trust Fabric decision’s disposition. Qualify the word when you use it. Read Four meanings of outcome.Delegated work
An agent can hand work to another agent: a sub-agent task, or a consultation in which it asks another agent a question. Both appear under Production → Delegated Work. A delegated run, by contrast, gives an agent a goal, a budget and a deadline rather than a fixed graph; start one from Production → Runs with + Delegated Run. Delegated work never holds a question for a person: an agent that needs a person asks through a human task.Files
Every Agent step receives two file tools:file_put stores a file and returns its file ID, and
file_get reads only the files the step is authorized to read. Steps pass file IDs to each other, not file contents. Read
Files and bindings.
Cost
Every run records the model usage and cost of its steps, and attributes it to the worker that did the work. Open a run to see its cost, and see totals under Analytics → Cost. Read Budgets and cost.Where you see it
- Forge Console
- HTTP API
- MCP
- Production → Workflows: the catalog, each workflow’s Graph, Versions, Runs and Schedule tabs, and the builder.
- Production → Runs: every run, with its graph, timeline, outputs, cost and trust receipt.
- Production → My Work: your open human tasks.
- Production → Approvals and Production → Delegated Work.
Related
Compose a workflow
Build a graph, choose node types and publish it.
Use the Workflow Architect
Describe the work and review the drafted graph.
Workflows in Console
Catalog, builder, versions and lifecycle.
Runs in Console
Inspect, cancel and rerun runs.
Approvals and human tasks
How Forge waits for people.
Observability
Watch runs and schedules in production.

