Password-Reset Event Notifications: Idempotency Keys for Email and SMS Retry Aud

<p>Short answer: put each user reminder on a queue, make the consumer idempotent, retry transient delivery failures with backoff, and move exhausted work to a dead-letter queue

<p>TL;DR: For Node.js event notifications, send transactional email first, poll its delivery status, and use SMS fallback only while the password-reset token remains useful. The

<p>Treat an SMS timeout as an unknown outcome, not a failed send: accept each password-reset event once, persist its expiry and idempotency key before dispatch, and retry only

<p>Short answer: use an emailed, single-use reset link as the default for most SaaS login recovery, and add SMS OTP only where users may genuinely lack email access or the product

<p>Most Playwright suites stop right before the hard part of a signup flow: the "confirm your email" link, the emailed 6-digit code, the password-reset mail. The usual reasons are

<p>Two things quietly decide whether a small application survives being used: whether its reads<br /> are indexed, and whether its writes can be repeated safely. They are usually

<p>Keep one searchable record per failure group, a bounded sample of its events, and immutable state transitions for resolution and rollback. That is the least complex admin page

<p>Email verification failures are hard to investigate. A user says the message never arrived, support sees a failed attempt, and an engineer opens logs full of addresses,