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

Create /bounce-list Endpoint #33

Open
2 tasks
nelsonic opened this issue Apr 16, 2020 · 2 comments
Open
2 tasks

Create /bounce-list Endpoint #33

nelsonic opened this issue Apr 16, 2020 · 2 comments

Comments

@nelsonic
Copy link
Member

nelsonic commented Apr 16, 2020

At present we only have a "Production" version of the Email App so the Dashboard is polluted with a lot of test data:
image

Todo

  • Create an endpoint that our Lambda function can query to check if a given email address has bounced in the past. If the status includes the word "bounce" then we do not attempt to re-send the email.
  • Additionally exclude the test@gmail.com email address and other known test emails from the dashboard.
@nelsonic nelsonic self-assigned this Apr 16, 2020
@nelsonic nelsonic added this to To do in dwyl app via automation Apr 16, 2020
@nelsonic
Copy link
Member Author

DISTINCT appears to work for grouping sent items to reduce the scrolling in the dashboard. 👍

SELECT DISTINCT ON (p.id, s.status_id) p.id as pid, 
s.id as sid, s.message_id, s.updated_at, s.template, s.person_id, s.status_id
FROM people p
JOIN sent s on s.person_id = p.id
GROUP BY (pid, sid)

@nelsonic
Copy link
Member Author

The dashboard is now grouped by the person.id and sent.status_id so we only see one entry per person for a given status of email. this means we don't have many entries for bounces for a given address.
image
I think there is still a lot more that can be done to make this dashboard more useful.
But It's only worth doing once we have Auth and the product working. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant