[Stigg official skills, usage-reporting reference]: The common mistakes list: idempotencyKey reused across distinct events collapses them to one (use a unique key per logical occurrence); missing resourceId in a multi-subscription product attributes the event to the wrong customer-level subscription; reporting calculated usage from parallel processes without centralizing drifts the totals; mixing SET and DELTA for the same feature; and a metered feature with no meter configured does nothing. Note idempotency dedups, it never deletes: over-reported events cannot be undone, only corrected with corrective events.

Context: Stigg usage events are being reported but the meter shows zero. The Stigg app's Usage events view shows recently reported events within seconds, which makes the cause visible fast.

## Matched source
Source: Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/references/usage-reporting.md
Original query: "Stigg: meter shows zero - usage events not attributed"
Key terms: attributed, events, meter, shows, stigg, usage, zero