Reuse the same transaction_id when retrying a failed ingest; duplicates inside 34 days are ignored, not double-counted. If you get a 409 on customer creation, the ingest alias is already taken, pick another or release it. For non-ingest POSTs, send Idempotency-Key so a retried request does not create a duplicate resource.

Context: Official docs (Metronome API idempotency): documents that transaction_id dedupes usage events over a rolling 34-day window, that reusing an ingest alias across customers returns 409 Conflict, that uniqueness_key conflicts also return 409 until released, and that the Idempotency-Key header caches POST responses for at least 24 hours.