> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Start, Run, and Monitor Event-Driven Workflows in Devset

> Start, monitor, and inspect live workflow executions in Devset, including real-time event logs and per-execution payload inspection.

Workflow Runs let you execute your saved workflows against a live broker and watch every emitted event in real time. When you start a run, Devset drives the workflow's pipeline stages in sequence, publishing messages to Kafka or RabbitMQ at each step according to the logic you built in the Flow Builder. Open Workflow Runs at [http://localhost:8082/runs](http://localhost:8082/runs).

## Starting a New Run

<Steps>
  <Step title="Navigate to the Runs home">
    Go to [http://localhost:8082/runs](http://localhost:8082/runs). The home screen shows two grids: **Active Runs** (workflows currently executing) and **Completed Runs** (finished, stopped, or failed executions).
  </Step>

  <Step title="Create a new run">
    Click **New Run**. A dialog opens with two required selections:

    * **Workflow** — pick the saved workflow you want to execute.
    * **Broker Connector** — choose the Kafka or RabbitMQ connector the workflow should publish messages to.
  </Step>

  <Step title="Start the run">
    Click **Start**. Devset initialises the run and it appears in the **Active Runs** grid with a status of `running`.
  </Step>
</Steps>

<Note>
  Devset supports a maximum of **10 concurrent runs** by default. If you have reached the limit, you must stop or wait for an active run to complete before starting a new one. You can raise this limit by setting the `DEVSET_ENGINE_MAX_ACTIVE_RUNS` environment variable (or the `devset.engine.max-active-runs` property) in your Devset instance configuration.
</Note>

## Monitoring Active and Completed Runs

The Runs home displays each execution as a tile card in one of two grids.

<CardGroup cols={2}>
  <Card title="Active Runs" icon="circle-play">
    Workflows that are currently executing or in the process of stopping. Tiles update in real time as the run progresses.
  </Card>

  <Card title="Completed Runs" icon="circle-check">
    Workflows that have finished, been stopped, or failed. Completed tiles are kept for review until you clear them.
  </Card>
</CardGroup>

Each tile shows the workflow name, the connector it is running against, the current status, and a timestamp. Click any tile to open the **Run Detail** view.

## Inspecting a Run in Detail

The Run Detail view streams execution progress live over a server-sent events (SSE) connection. You see the event log update in real time as each pipeline stage completes and each message is emitted.

<Steps>
  <Step title="Open the Run Detail view">
    Click a run tile on the Runs home. The detail view opens showing the execution progress and an event log.
  </Step>

  <Step title="Review the event log">
    The event log lists every event emitted during the run in chronological order. Each entry shows the stage that produced the event, the broker target, and a timestamp.
  </Step>

  <Step title="Inspect individual events">
    Open the **Events** panel to drill into per-execution detail. Click any log entry to see the full headers and payload of that specific emitted event.
  </Step>
</Steps>

## Stopping a Running Workflow

To stop a workflow before it completes naturally, open the Run Detail view and click **Stop**. Devset sends a graceful stop signal — the run transitions through `stopping` before settling on `stopped`. In-flight stage executions are allowed to finish before the run halts.

## Run Status Lifecycle

Every run moves through a defined sequence of statuses:

<Accordion title="Status flow diagram">
  ```text theme={null}
  idle → running → stopping → stopped
                ↘ completed
                ↘ failed
  ```
</Accordion>

| Status      | Meaning                                                               |
| ----------- | --------------------------------------------------------------------- |
| `idle`      | The run has been created but execution has not begun.                 |
| `running`   | The workflow is actively executing stages and emitting events.        |
| `stopping`  | A stop was requested; Devset is waiting for in-flight work to finish. |
| `stopped`   | The run was halted before completion by a user-initiated stop.        |
| `completed` | All pipeline stages executed successfully.                            |
| `failed`    | The run encountered an unrecoverable error and halted.                |

<Warning>
  A `failed` run does not automatically retry. Open the Run Detail view to read the error in the event log, fix the underlying issue in your workflow or connector configuration, and then start a new run.
</Warning>

<Tip>
  Use the [Kafka Live](/guides/kafka-live) view alongside an active run to watch dispatched messages land on the topic in real time. Open both in separate browser tabs for a side-by-side view of your workflow output.
</Tip>