# Running a service

*How to trigger a run, and what happens during one.*

## Trigger modes

Every service resolves to one of three trigger modes:

  - **Manual** — Run on demand from the service page or API.
  - **Schedule** — Run on a cadence (e.g. hourly, every N days).
  - **Event** — Run when a connected tool fires an event (webhook or connector event).

If nothing is armed, a service defaults to **manual**.

## Setup steps

Before a run starts, Tredy shows any **setup steps** it needs — connectors to
link, a reviewer to assign, documents to provide. Resolve them inline, then run.

## During a run

A run moves through stages and can be **paused**, **resumed**, or **cancelled**.
When a real decision is required, the run enters a **human-in-the-loop** state:
it surfaces the question, waits for your answer or edit, and continues.