The health report answers one question — "is my project healthy, and if not, is the problem my code or the platform?" — with a deterministic verdict, not a dashboard. The server computes the verdict from your telemetry; no LLM interprets it, so the same numbers always produce the same answer.

Every report reads a live window of your project's data and returns a headline verdict, the evidence behind it, and a single suggested next action. The only report today is health.

The report splits a project into three dimensions, each with its own verdict:

Splitting Flow from Execution is the point: a project can be failing to start work (Flow) while every run that does start completes fine (Execution), or the reverse. The report names which one, so you know whether to look at your concurrency settings or your task code.

Each dimension carries a severity — healthy, degraded, or failing — and the report leads with the worst one as its headline. The headline finding is expanded with its supporting metrics; the others collapse to a one-line verdict.

Here is trigger report health for a project whose runs are backing up against the environment concurrency limit:

/report health        prod · last 1h · vs 7d normal

✕ Flow stalled — at your env concurrency limit for the last 40 min

  concurrency     100/100           ▄▅▆▇████   40 min at limit
  pending         1,240      ↑ 6×   ▁▂▄▅▆▇██   (normal ~120)
  start latency   p95 8.2s   ↑ 4×   ▁▂▃▄▆▇██   (normal ~2s)

  why:  runs are finishing at ~90/min
        nothing dead-lettered

✓ EXECUTION   runs are executing normally

✓ LIVENESS    fresh — telemetry current, updated 12s ago

  read: limit saturated → incoming work exceeds capacity → backlog grows

→ Raise the env concurrency limit
  Read concurrency docs
  or do nothing — backlog drains in ~26.7 min once triggers ease

The verdict reads top to bottom:

• Headline — the worst finding, stated as a verdict with the breach window. Here Flow is stalled because concurrency has been pinned at its limit for 40 minutes.
• Evidence — the metrics behind the headline, each with a sparkline over the window, its movement against your baseline (↑ 6× means six times normal), and an annotation (40 min at limit) or baseline (normal ~120).
• why: — the facts that support the verdict, including what the problem isn't (runs are still finishing, nothing is dead-lettered — so it's not your code).
• Sibling findings — Execution and Liveness, each a one-line verdict.
• read: — the causal chain in one line.
• Next steps — the primary action first (→), then any alternatives.

Every surface carries meaning in glyphs, never color alone, so the report is legible in a monochrome terminal or a plain-text MCP host:

The same report renders four ways.

Print an interpreted report for an environment. The command defaults to the health report and the prod environment — a manual production check.

npx trigger.dev@latest report health --env prod --period 24h

The command prints only the report — no banner — so it pipes cleanly. Output is ANSI-colored in a real terminal and plain markdown when piped:

trigger report health > health.md   # markdown, no escape codes

Color follows the supports-color convention: NO_COLOR (any value) or FORCE_COLOR=0 disables color outright; FORCE_COLOR set to anything else force-enables it. Both win over TTY detection — which matters for agents spawned on a PTY, where isTTY is true but escape codes would be garbled.

Fetch the report from an AI coding tool through the Trigger.dev MCP server. The tool returns plain markdown by default, or ANSI when color is set (for hosts that display escapes in tool output). It is read-only.

The MCP server also registers a report prompt, which hosts that support MCP prompts surface as a slash command (Claude Code renders it as /mcp__trigger__report). Running /report health calls get_report for you and shows the result verbatim in a fenced code block, preserving the monospace alignment and sparklines.

The endpoint behind every surface. It accepts a period and a format, and authenticates with an environment secret key or a JWT scoped to read the report's query tables (read:query).

format=markdown and format=ansi return the rendered text. format=json returns the ReportViewModel — the semantic payload behind the render, where verdicts are codes rather than prose, for building your own surface on top of the report.

curl "https://api.trigger.dev/api/v1/reports/health?period=24h&format=json" \
  -H "Authorization: Bearer $TRIGGER_SECRET_KEY"

The environment comes from the key. Use an environment secret key, or a JWT scoped read:query for the report's tables. Personal access tokens are not accepted.

An unknown report key returns 404 with the list of available keys.