We have had a break in the cold case of messages coming from incorrect and more than one service numbers. A GSA team started using Notify to text staff and learned after sending out their first batch that the texts are coming from multiple numbers.
Cliff traced through the code and added a bunch of debug, but was never able to repro and we stopped hearing about it from users. I added the experimental validation that should have blocked messages with the wrong sender number but apparently is not doing so. The issue is that this was happening a few months ago, but when we went to investigate, it stopped happening. And now it's started up again.
The check was put in based on thought experiment since we can't seem to reproduce ourselves.
Next step:
[ ] We believe this is an AWS problem, not our code, need to contact them.
[ ] Also - can we find some way to repro this? Maybe if we send a dozen messages to ourselves and actually look at the sender phone number, we'll see it happen at some point.
We have had a break in the cold case of messages coming from incorrect and more than one service numbers. A GSA team started using Notify to text staff and learned after sending out their first batch that the texts are coming from multiple numbers.
Here are some of the different numbers that people were getting the texts from: 844-734-2791 888-904-6435 888-840-2596 844-734-2791 844-795-2263 (833) 595-1552
Work-to-date
Related issue:
Cliff traced through the code and added a bunch of debug, but was never able to repro and we stopped hearing about it from users. I added the experimental validation that should have blocked messages with the wrong sender number but apparently is not doing so. The issue is that this was happening a few months ago, but when we went to investigate, it stopped happening. And now it's started up again.
The check was put in based on thought experiment since we can't seem to reproduce ourselves.
Next step: