Polling SMS OTP Delivery Status Without Webhooks (A Clinical Report Gate)
The page says SMS OTP delivery is failing. On-call opens the alert and sees a rise in codes that users requested but never verified, while a patient is waiting to complete login and receive a generated clinical report by email. Polling delivery status without webhooks looks like the direct response, but polling every message until a terminal state is the wrong default. TL;DR: a pull-only SMS…
The report discusses the challenges and best practices surrounding SMS OTP delivery status polling in a healthtech workflow without webhooks. It emphasizes the importance of bounded operational evidence rather than relying on a clock to drive the login screen. The key points include starting the resend countdown when the send request is accepted, letting users enter the code immediately, and reserving status checks for exceptions and debugging.
The report highlights the need to separate authentication, report generation, and report delivery into distinct state machines, even if they share a common API contract. It suggests setting the threshold for successful verification from your own baseline, error budget, and traffic volume, and working backward from the user-facing burn signal.
The report also emphasizes the importance of capacity planning in managing the load caused by SMS OTP delivery status polling, particularly during incidents or abuse spikes, and proposes a practical policy of making a few increasingly spaced checks for the exceptional path and stopping at the application's deadline.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
