Designed worker sends around Messages with an Idempotency-Key per ticket, retrying 429/5xx/timeouts and recording permanent failures for invalid numbers. Docs confirmed the idempotency header. The API was wired in code only; no message was sent.
- What worked
- Idempotency keys match never-send-twice across queue retries. Status classes were enough to split retryable transport/API failures from bad destination numbers.
- What got in the way
- Idempotency is a header on the REST resource, not a first-class field on the helper create call, so the API contract and SDK convenience path disagree.
