---
title: "Run and monitor workflows"
description: "Execute workflows, watch live progress, approve gates, and read run reports."
canonical: https://ocho.bot/docs/flows/run-and-monitor
last_updated: 2026-07-12
---

# Run and monitor workflows

> Execute workflows, watch live progress, approve gates, and read run reports.

## Run from the editor

Click **Run** in the editor toolbar. Ocho saves any unsaved changes first, then starts the run immediately — there is no compile or validation step and no warnings prompt. A **Run started.** toast confirms it, and the editor's right-side panel switches from the Assistant to the **Run** panel with live progress (use the Assistant/Run toggle to switch back).

Blocks that can't run don't warn you up front — the block itself fails during the run, and any blocks downstream of it are marked **skipped**. If other blocks still succeeded, the run ends as a partial failure; if nothing succeeded, it ends as failed.

## The run panel

- **Status** — queued, running, awaiting approval, succeeded, partial failure,

or failed. Updates stream in live, typically within a second or two.

- **Run report** — every finished run gets a report, even if it's just

"ran N steps in Xs". Summary chips sit above the rendered markdown report:   **Duration** and **Steps** always show, **Items** appears when the run had   loop iterations (shown as succeeded/total), and **Errors** and **Warnings**   appear only when non-zero. Scratchpad blocks add extra markdown sections to   the report.

- **Event timeline** — each block's start, success, failure, or pause, in

order. Shows "No events yet." until the first event arrives.

## Approve a Human Gate

When a run hits a Human Gate block, its status becomes **awaiting approval** and an **Approve** button appears at the top of the run panel. The run resumes once approved. There is no reject button — an unapproved run simply stays paused.

## Runs history

The **Runs** tab on the Flows page lists recent executions. Each row shows a status badge, the workflow (identified by the first characters of its ID, or **Ad-hoc** for runs without one), the trigger kind when one was recorded, and the created-at timestamp; failed runs also show a short error summary.

Click a run to open its panel in a dialog — report and event timeline, plus an **Open in Editor** link to the workflow. Ad-hoc runs have no workflow, so no link.

## Run a workflow proposed in chat

Chat can sometimes propose a workflow as a card in the conversation ("Run this multi-step workflow?"). More often it answers with a plain text blueprint instead — a blueprint is not executable. When the proposal card does appear, it offers:

- **View** — a read-only preview of the proposed canvas.
- **Edit on Canvas** — turns the proposal into a real workflow and opens the

editor.

- **Run** — also turns the proposal into a real workflow (it appears in your

Workflows list), then executes it right there, with the run panel embedded   in the card.

Proposals never run on their own.

## Good to know

- Runs can't be cancelled once started; a stuck run can sit at awaiting

approval indefinitely without harm.

- The history shows the most recent 50 runs.
- If you refresh the chat page, a proposal card goes back to its original

unrun state — it forgets it was ever run or promoted. The run itself   continues and remains visible under the Runs tab. Clicking the card's   **Run** again runs the same workflow a second time — Ocho remembers the   workflow it already created, so no duplicate appears in your Workflows list.

All docs: https://ocho.bot/docs

---

Ocho — AI knowledge orchestration · [Home](https://ocho.bot/) · [Docs](https://ocho.bot/docs) · [Blog](https://ocho.bot/blog) · [About](https://ocho.bot/about) · [Developers](https://ocho.bot/developers) · [Contact](https://ocho.bot/contact) · [llms.txt](https://ocho.bot/llms.txt)