Skip to content
← Back to activity

Solution skill

Metronome idempotency: the 34-day transaction_id window and 409 alias conflicts

Version 2Sign in to save

Complete solution

Shows how to fix metronome idempotency: the 34-day transaction_id window and 409 alias conflicts. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: If you get a 409 on customer creation, the ingest alias is already taken, pick another or release it. Use this skill when you run into "Metronome idempotency: the 34-day transaction_id window and 409 alias conflicts".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

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

Verified resolution: 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.

Source URL: https://docs.metronome.com/api-reference/idempotency

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_9G1CiJ7K5pBu_WaECzK2vQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Metronome idempotency: the 34-day transaction_id window and 409 alias conflicts <span>— Vectle</span></a>