Metronome billing-doctor error codes: timestamp, duplicate transaction, bad aggregation key

[billing-doctor docs]: TIMESTAMPINVALID means the timestamp field is malformed; check the ISO 8601 format and valid date values. DUPLICATETRANSACTIONID is the dedup guard firing: when uniqueid matching is on, resending an event with the same uniqueid produces a new error object but is not a duplicate event, so use genuinely unique IDs per event or batch idempotent events in one call. AGGREGATIONKEYINVALID means the aggregationkey is not a valid property or groupby key for the billable metric, so confirm the key exists in the metric definition. TIMESTAMPOUTOFBOUNDS marks data outside the 34-day backdating window.

Context: Three billing-doctor errors that map to specific event-payload defects.

Matched source

Source: Source: https://github.com/thedaviddias/billing-doctor/blob/HEAD/docs/metronome/errors.md Original query: "Metronome billing-doctor error codes: timestamp, duplicate transaction, bad aggregation key" Key terms: aggregation, billing, codes, doctor, duplicate, error, metronome, timestamp, transaction

Source: Three billing-doctor errors that map to specific event-payload defects.

Verified resolution: [billing-doctor docs]: TIMESTAMPINVALID means the timestamp field is malformed; check the ISO 8601 format and valid date values. DUPLICATETRANSACTIONID is the dedup guard firing: when uniqueid matching is on, resending an event with the same uniqueid produces a new error object but is not a duplicate event, so use genuinely unique IDs per event or batch idempotent events in one call. AGGREGATIONKEYINVALID means the aggregationkey is not a valid property or groupby key for the billable metric, so confirm the key exists in the metric definition. TIMESTAMPOUTOFBOUNDS marks data outside the 34-day backdating window.

Source URL: https://github.com/thedaviddias/billing-doctor/blob/HEAD/docs/metronome/errors.md