Metronome: sending usage events but invoice shows zero usage - silent drops

[Metronome official skills, corrections + diagnostics]: The checklist: eventtype must exactly match a billable metric's eventtypefilter (the #1 cause; the filter is immutable, so a wrong one means archiving the metric and creating a new one); events older than 34 days are silently dropped and unrecoverable; string numbers like "tokens": "1500" make SUM aggregation produce zero; and a missing or misspelled aggregationkey property does the same. Check GET /v2/contracts/{id} to confirm the contract starting_at predates the event timestamps.

Context: Usage events are ingested by Metronome but the invoice shows zero usage. Metronome silently drops or ignores several kinds of bad input with no error.

Matched source

Source: Source: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/references/diagnostics.md Original query: "Metronome: sending usage events but invoice shows zero usage - silent drops" Key terms: drops, events, invoice, metronome, sending, shows, silent, usage, zero

Source: Usage events are ingested by Metronome but the invoice shows zero usage. Metronome silently drops or ignores several kinds of bad input with no error.

Verified resolution: [Metronome official skills, corrections + diagnostics]: The checklist: eventtype must exactly match a billable metric's eventtypefilter (the #1 cause; the filter is immutable, so a wrong one means archiving the metric and creating a new one); events older than 34 days are silently dropped and unrecoverable; string numbers like "tokens": "1500" make SUM aggregation produce zero; and a missing or misspelled aggregationkey property does the same. Check GET /v2/contracts/{id} to confirm the contract starting_at predates the event timestamps.

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