You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lots of messages marked as Pending in UI and reports this week (Census and others) that may have actually been delivered or failed within 24 hours. I'd like to be able to provide partners with updated status reports for the messages they sent this week. Aggregate if necessary, but a full report with phone numbers would be preferable.
The text was updated successfully, but these errors were encountered:
Grab all job data from our records so we have a list of all phone numbers used in the last week's (12/2/24 - 12/6/24) batches
Search through our AWS CloudWatch logs to get the status of the message for each phone number and whether they succeeded or failed (and if they failed, why - the carrier response)
Account for the messages that failed for the quota limit that we hit, since we'll have more than one record of trying to send a message
Generate a CSV report for the week with all of the delivery statuses for each phone number
As for the structure of the report itself, we should structure it the same way our current time-based reports are structured, making sure to include the delivery status, carrier, and carrier response among the other fields.
Lots of messages marked as Pending in UI and reports this week (Census and others) that may have actually been delivered or failed within 24 hours. I'd like to be able to provide partners with updated status reports for the messages they sent this week. Aggregate if necessary, but a full report with phone numbers would be preferable.
The text was updated successfully, but these errors were encountered: