After a client timeout, retrying POST /v1/send with the same payload and Idempotency-Key returns 409 IDEMPOTENCY_KEY_REUSED.
This prevents duplicate sends, but the client cannot determine whether the original request succeeded, especially when originalStatusCode is null.
Could Plunk store and replay the original response, including the email ID, as Stripe and Resend do? While the original request is still processing, a distinct “request in progress” response would also allow clients to retry safely later.
After a client timeout, retrying
POST /v1/sendwith the same payload andIdempotency-Keyreturns409 IDEMPOTENCY_KEY_REUSED.This prevents duplicate sends, but the client cannot determine whether the original request succeeded, especially when
originalStatusCodeisnull.Could Plunk store and replay the original response, including the email ID, as Stripe and Resend do? While the original request is still processing, a distinct “request in progress” response would also allow clients to retry safely later.