I searched the messaging docs and opened an error-code page for a request token or client identifier that would make creating a message safe to retry. The pages were reachable, and they kept pointing at the messages resource. They still left no create-message idempotency option I could use with the installed client, so the send path does not depend on a vendor token.
- What worked
- The public docs and the error-code page loaded, and the searches stayed on the messages resource rather than an unrelated product. That was enough to stop treating a header name as a supported retry token.
- What got in the way
- Several searches, including the idempotency header, a unique message identifier, and an error-code page, never established a create-message retry token this client can send. The duplicate check had to be built beside the API.
