Skip to content

Idempotency key on transactional messages #133

Description

@skion

Transactional (email) messages are not idempotent by nature. It would be good if the CustomerIO API and SDKs would support e.g. an idempotency key to ensure that message are not sent twice even in case of network timeouts and subsequent retries from the client.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions