## TL;DR

The ordered checklist is event_type mismatch (the #1 cause: event_type does not match any billable metric's event_type_filter, events silently ignored), wrong customer_id or missing ingest alias, events older than 34 days (silently dropped), contract starting_at in the future, and genuinely inactive customer.

## Fix

1. The ordered checklist is event_type mismatch (the #1 cause: event_type does not match any billable metric's event_type_filter, events silently ignored), wrong customer_id or missing ingest alias, events older than 34 days (silently dropped), contract starting_at in the future, and genuinely inactive customer.
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this Metronome feature.
- The symptom matches: zero-usage contract - diagnostic order for events not billing.

## When NOT to use

- Unrelated Metronome issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Metronome. Source: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/references/diagnostics.md.

## Variant phrasings

### zero-usage contract - diagnostic order for events not billing

## Why it happens

A customer's invoice shows zero usage even though events are being sent. Metronome silently drops bad events, so check in likelihood order.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/references/diagnostics.md