-
Notifications
You must be signed in to change notification settings - Fork 9
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
BUG: v3 POST email does not send the email #1501
Comments
Cris says that SMS is not affected. |
Hey team! Please add your planning poker estimate with Zenhub @babyjunior56 @cris-oddball @EvanParish @k-macmillan @kalbfled @ldraney @nikolai-efimov |
Fixed the issue by removing the extra decorator. Tests are failing for unrelated reasons. At least two packages underwent major version upgrades and it is breaking tests. |
PR approved and merged deployed to Perf. Manually testing the route until I can finish the automation. |
The delivery status in v2 does return a 200 OK, but the delivery status is never updated to Delivered, it is at Sent. I do note this in the Description but am asking a clarifying question of the team before I close this ticket. |
The delivery status will be handled on #1616. Closing this ticket. |
Description
After this commit, 4bcb990, v3 email was able to send email messages and receive a sent status.
After this commit, 24d8664, v3 email still could POST the request, get a 202, create a notification_id but it never sends the message and the GET route returns a 404. The logs really do not show much of anything, other than that the POST request happened.
Steps to Reproduce
Using the same payload with the v2 POST v2/notifications/email route, observe the 201 response for the POST and using the GET v2/notifications/{{notification-id}} route observe the 200 response and an eventual 'delivered' status.
Workaround
Is there something we can do to work around this issue in the meantime?
No.
Impact/Urgency
Please note - it is critical we finish this work after the new year. Remaining V3 work should not be a code overhaul. Any refactoring requests must be approved by Product and Tech Lead.
High - v3 email cannot be user or automated until this is fixed.
Expected Behavior
QA Considerations
Additional Info & Resources
The text was updated successfully, but these errors were encountered: