Skip to main content

Missions

A mission is a single run of a workflow. It records the inputs, every node's status and output, the agents' conversations, approvals, token usage, cost and timing. You watch it live on the execution canvas and review it later from mission history.

Go to Build → Missions to launch and review missions.

How missions are created​

StartRecorded trigger
Launched from Missions, or Run Workflow in the builderManual
A workflow scheduleSchedule
A webhook deliveryWebhook
A program activityProgram
The Platform APIAPI
Claude Code, through the Platform MCP serverClaude Code
A parent workflow's Mission nodeIts own child mission, started by the workflow

The Missions page​

The page has three parts:

  • Start a Mission — a workflow picker shown as the page title. If the project has no workflows, it says Nothing to launch yet with a Create a workflow button.
  • The launch form — the selected workflow's attributes: text boxes, drop-downs, checkboxes and buttons, plus the launch button (Launch Mission, or the workflow's own trigger button, such as Go).
  • Recent runs — your latest missions, with Refresh and View all history.

Selecting a workflow pre-fills its default values. A workflow with no attributes launches as soon as it is selected.

You need the project Editor role, or a run grant for the workflow, to launch it. Otherwise the page says "You do not have permission to run this workflow."

See Your First Mission for a walkthrough.

The execution canvas​

Launching a mission, or opening one from history, shows the execution canvas — the workflow laid out as a live graph.

Header: a breadcrumb (Missions, then Program and Workflow when relevant), the mission name, a progress bar (hover for "N% complete", or "Paused — action required" when an approval is waiting), a count of active nodes, and the live-update status: Live, Connecting, Offline or Error. Back to missions or Escape returns to the Missions page.

Each node shows its status:

StatusMeaning
WaitingNot reached yet.
RunningIn progress. Agent and team nodes show what they're doing ("Reasoning...", "Processing...", "Generating response...") and recent tool calls.
CompletedFinished.
FailedFailed. The message explains why.
SkippedOn a Condition branch that wasn't taken.
Action RequiredWaiting for an approval. Approve and Reject buttons appear on the node.

On a node you can:

  • View live output / View output — expand the node's output, and Copy output.
  • Open in Chat (agent and team nodes) — open the node's conversation in the chat panel, where you can read the full exchange and talk to the agent.
  • Stop node — end the node's agent session.
  • Click the node to open its conversation in the collaboration pane.

The side rail has three views: Stages (each step and its status, with Open conversation), Timeline (a running log of events) and Conversation ("Talk to the team running this mission").

When a run you were watching finishes, FYAI shows a completion message with a Schedule it action that opens the workflow so you can add a schedule.

Mission status​

Mission history labelExecution history labelMeaning
ActiveRunningIn progress — including while paused at an approval.
CompletedCompletedEvery reachable node finished.
FailedFailedA node failed, an approval was rejected or timed out, a tool call that needed approval was never approved, a Kill Switch stopped the run, or the server restarted mid-run.
Needs inputWaiting on youThe mission's status was set to waiting for a person through the API.
FailedStoppedThe mission's status was set to stopped through the API.

A run that a Kill Switch halts, or that skipped an unapproved tool call, ends Failed rather than Completed so that the gap is visible.

Approvals during a mission​

Missions pause for people in two ways:

  • Approval nodes in the workflow.
  • Tool calls that need approval — when an agent wants to use a function whose approval setting requires it.

Both show on the node as Action Required and as an alert in the Alerts panel (the bell in the header), where you can Approve or Reject without opening the mission. Approval node requests survive signing out. See Using Approval Gates.

Mission history​

View all history opens the Mission history panel:

  • All missions or This workflow (name).
  • Search runs, phases and workflows.
  • Filter by status (Active, Needs input, Completed, Failed), by workflow (Any workflow), and by date (Any time, Last 24h, Last 7 days, Last 30 days). Clear resets the filters.
  • Runs tab — missions grouped by day (Today, Yesterday, …). Each has Resume mission (for active runs) or View mission, Re-run this mission (launch again with the same attribute values) and Delete mission.
  • Scheduled tab — the project's workflow schedules, with next and last run times and failed-run counts. Edit or delete them here. See Scheduling Workflows.

Each workflow's own runs are also listed in the builder under Executions — see Designing Workflows.

Sub-workflow missions​

A Mission node in a workflow starts the chosen workflow as its own mission and waits for it. The child mission has its own canvas and history entry. It receives the parent node's input message, not the parent's attribute values.

Mission configurations (API only)​

The API has a /mission-configurations resource for saving named presets — a workflow plus attribute values. The Missions page doesn't use them.