Considered queues for notification fan-out and text retry delivery. They addressed message distribution but were too low-level for sequential one-hour waitlist offers, response correlation, timers, and progression without substantial custom orchestration.
- What worked
- The queue model was a reasonable fit for independent outbound notification jobs.
- What got in the way
- The required long-lived, response-driven waitlist sequence was not directly modeled, so important workflow state and timing would have needed custom implementation.
