Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle unsuccessful deliveries #2077

Merged
merged 2 commits into from
Nov 20, 2024
Merged

Conversation

mattwr18
Copy link
Contributor

@mattwr18 mattwr18 commented Nov 20, 2024

Fixes #2076

What changed and Why

This PR extends the same feature we had with Twilio to 360dialog, we:

  • Look out for statuses that show failed message delivery that have an error code of 131_026, which indicates that we cannot message this recipient for one of several reasons. See issue for a list of them from Meta.
  • When we get this error, we mark the contributor as inactive since we cannot send them any messages,
  • Then, we create a notification to make this visible to the users
  • Also, we add some text on the contributor show page with this information ☝️ ...

This is all an attempt to not silently treat these issues. We want to bring visibility to who we know cannot receive messages and allow the clients to decide if they would like to work with the contributor to resolve the issue.

@mattwr18 mattwr18 merged commit fdbe579 into main Nov 20, 2024
1 check passed
@mattwr18 mattwr18 deleted the 2076_handle_unsuccessful_deliveries branch November 20, 2024 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[improvement] Handle message undeliverable errors
1 participant