Delivery metrics

Read a project's delivery flow — throughput, cycle time, time per stage, aging work, and how much of the automation held without rework.

Use Metrics to understand delivery speed, waiting work and rework. The figures come from cycle stage history, the record of status changes and their timing.

Prerequisites

Agency role with manage access on the project.
At least one recorded cycle transition to populate the metrics.

Reading it

In the dashboard, open the project’s settings window, then Usage → Metrics. Over the API:

curl -sS "$HLIX_BASE_URL/v1/api/projects/$PROJECT_ID/cycle-metrics" \
  -H "x-api-key: $HLIX_API_KEY" \
  -H "X-Organization-Id: $HLIX_WORKSPACE_ID"

Metrics cover the project’s lifetime. Durations use milliseconds in the API and formatted time in the dashboard.

What each number means

Throughput

Counts of cycles by where they ended up: completed, failed, and canceled. These are lifetime counts.

completed counts every cycle that reached the terminal success status, done (older cycles reading pr_created count the same way).

The dashboard shows completed as the headline figure with failed and canceled beneath it.

Cycle time

p50 and p90 measured from a cycle’s creation to its last recorded transition, over cycles that reached a terminal status — done, failed or canceled.

sampleSize counts terminal cycles with recorded stage history. An empty sample returns null percentiles, shown as — in the dashboard.

Time per stage

The median duration of completed visits to each stage. A visit is counted once the cycle leaves the stage.

The chart follows lifecycle order and includes stages with completed visits. Older Interviewing stages remain visible; pr_created time appears under Done.

Work in progress and aging work

WIP counts cycles currently in flight — draft, triage, planning or executing — broken down by stage.

Review is measured separately under Time per stage. WIP and aging work cover the stages listed above.

Aging work lists in-flight cycles whose current stage exceeds that stage’s historical median for the project, sorted by largest overrun. A stage needs completed visits before Hlix can calculate that threshold.

Automation quality

This section measures how often the automation got it right the first time.

Every stage exit — a cycle leaving one stage — is attributed to a human, an agent, or a rule. Agent and rule both count as automated.

Figure	What it is
Raw automated share	Automated exits ÷ all exits
Quality-adjusted share	Clean automated exits ÷ all exits

An automated exit is clean when the cycle stays out of that stage for the rest of its lifecycle. Returning to the stage counts as rework.

A cycle can reach done after rework. Those repeated stages still reduce its quality-adjusted share, which measures how often automated decisions held the first time.

If a panel looks wrong

“No cycles yet” on a project you know has run work. Metrics reads cycles, not tasks. A project whose work never became a cycle has nothing to measure.
Every stage median is missing. Nothing has exited a stage yet. A cycle sitting in executing since it was created has produced no closed segment.
Cycle time is — but throughput shows completed cycles. Those cycles reached a terminal status with no stage-history entries to measure between, so the sample is empty.
Aging work is empty while something is obviously stuck. That stage has no median yet, so there is no threshold to exceed. It will start flagging once comparable cycles have passed through.
The Metrics entry is missing from the navigation. You are signed in as a portal client. Metrics is agency-only.