Duplicate XML Elements on Retry After Transient Failure - Idempotency Key Versus Schema Constraint

This question addresses the appropriate enforcement layer for idempotency when XML write operations are retried following a transient communication failure.

Application-level idempotency keys risk collision if not globally unique, and not all XML serializers preserve user-defined ID attributes through round‑trips, potentially invalidating dedup checks. Schema-level unique constraints on XML ID attributes can prevent duplicate insertion but may require transaction coordination across distributed nodes and are not universally supported by XML processing pipelines.

Can a consistent strategy guarantee no duplicate XML elements across retries without single points of failure? Does the choice depend on whether storage enforces unique constraints on the XML ID attribute? Can a hybrid approach reconcile application-level keys with schema‑level guarantees in stateless environments?