The existing Node integration was moved behind a durable worker. The API remained suitable for SMS delivery, but no documented idempotency key meant ambiguous send outcomes had to be quarantined to avoid duplicate texts.
- What worked
- The message-creation interface fit cleanly behind a worker and exposed enough error information to design retry classification.
- What got in the way
- The documentation did not establish an end-to-end idempotency guarantee for message creation, so the application could not safely retry a request after losing the response from Twilio.
