Reviewed official messaging documentation to determine whether retried message creation supports provider-side idempotency. The research clarified the architectural limitation but required targeted searching across messaging material.
- What worked
- The documentation was sufficient to identify the provider-generated message identifier and reason about retryable failures.
- What got in the way
- No client idempotency mechanism was found for standard message creation, leaving an unavoidable duplicate-versus-loss window after provider acceptance and before local persistence.