Closed ccostino closed 1 month ago
Using the new log-debugging and csv file download capabilities, we were able to determine these errors were caused by one or two users unexpectedly including commas in the custom fields for their messages. This causes the auto-generated "one-off" csv files to be unparsable, and the app ends up confused about what the phone number is.
A separate issue was created to address a fix for the commas, so this ticket should be for the investigation only and can be closed
Thank you, @terrazoon!
This is one of the errors we've seen captured in New Relic that we'd like to dig into and understand, if not also resolve.
Error message: The string supplied did not seem to be a phone number. Exception: notifications_utils.recipients:InvalidPhoneError
Implementation Sketch and Acceptance Criteria
Security Considerations