Skip to main content

Running Executions

An execution is a single run of a squad. Every time a squad runs, whether started manually or by a trigger, Obi creates an execution record that tracks the status, progress, and results.

Starting an Execution​

There are two ways to start an execution.

Manual Execution​

  1. Open a squad in the visual editor.
  2. Click the Execute button.
  3. Obi creates the execution and begins running the workflow immediately.

Triggered Execution​

When a trigger fires (an email arrives, an API request is received, or a Linear task is delegated), Obi automatically creates an execution for the squad linked to that trigger. See Setting Up Triggers for details.

Execution Statuses​

Each execution moves through a series of statuses:

  • Queued means the execution has been created and is waiting to start.
  • Started means the squad is actively running. Agents are processing in the order defined by the workflow graph.
  • Completed means the squad finished successfully. The results are available.
  • Error means the squad encountered a problem and could not finish.
  • Killed means someone manually stopped the execution before it completed.
  • Input Required means the execution has paused because an agent needs additional input from you before it can continue.

Monitoring an Execution​

Open the Executions page from the sidebar to see all executions across your workspace. Click on any execution to see its details.

The execution detail page shows:

  • Status and a timer showing how long the execution has been running.
  • Visual graph showing which agents have run, which are currently active, and which are still pending.
  • Logs and traces in the sidebar, providing a detailed record of what each agent did.
  • State inspection for viewing the data flowing through the workflow.

Obi updates the execution page in real time using live connections, so you can watch progress without refreshing.

Providing Input​

Some workflows include agents that require human input at certain points. When this happens, the execution pauses with a status of "Input Required."

  1. Open the paused execution.
  2. An input form appears showing which values are needed.
  3. Fill in the requested information and submit.
  4. The execution resumes from where it left off.

Executions waiting for input also appear on the workspace dashboard so you can quickly find and respond to them.

Stopping an Execution​

If you need to cancel a running execution:

  1. Open the execution detail page.
  2. Click the Stop button in the header.
  3. The execution status changes to "Killed" and all processing stops.

Stopping an execution cannot be undone. If you need to run the same workflow again, start a new execution.

Viewing Execution History​

The Executions page shows a searchable list of all past and current executions. You can filter by app, squad, or status to find specific runs.

Each entry in the list shows the execution identifier, status, and duration. Click any entry to view its full details, logs, and results.

The workspace dashboard also provides quick access to recent executions, including cards for currently running executions, those needing input, recent failures, and recent successes.