Closed gabrielecipriano closed 5 years ago
We finally understood that the messages were not being sent because we were sharing the same database between our local test and CI. That meant that notifications app from different foundations were picking each other jobs and failing to deliver for unrecognised UUID. It also explains why we could find logs for failed deliveries.
Summary When using notification service to deliver emails in a CF space (calling
/space/<spaceID>
endpoint) most of the time the emails fail to be delivered.Expected behaviour Every time the space endpoint is called, each user of the space should receive an email.
Actual behaviour Most of the time the space endpoint is called emails are not delivered to any of the user.
Notes We are consuming the notification app as part of the v57 of notifications-release. It is pushed via the errand
deploy-notification
.Steps to reproduce
/space/<spaceID>
.queued
for each email in the space.messages
in DBnotifications
.Manifest properties
Logs When the email is delivered
When the email is not delivered
Versions Notification release: v57 Notification app: v1.1.0 SMTP server: Mailhog CF-CLI: v1.16.0 DATABASE: MYSQL innodb v5.7.14