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
Another concern is that we don't have a way of saying this message was tried XYZ amount of times, and it's obviously something seriously wrong with it. Aka the poison pill problem in microservices. I noticed it because I monitor AWS/Lambda Errors across all functions.
I think if unee-t/frontend#797 was dealt with, this problem would go away, because then there would be a clear request and error response for @nbiton's MEFE to act on.
The text was updated successfully, but these errors were encountered:
https://ap-southeast-1.console.aws.amazon.com/cloudwatch/home?region=ap-southeast-1#logEventViewer:group=/aws/lambda/invitefromqueue_invite;filter=%223aba5cd8-2203-53df-be24-093967a1df40%22;start=P1D
This payload seems to repeatedly trigger an error between MEFE & the Invite lambda.
I'm assuming it's some failure wrt to procedure the invite lambda calls with that payload, hence the bug report here.
https://s.natalian.org/2019-08-30/invite-dev-error.mp4
Another concern is that we don't have a way of saying this message was tried XYZ amount of times, and it's obviously something seriously wrong with it. Aka the poison pill problem in microservices. I noticed it because I monitor AWS/Lambda Errors across all functions.
I think if unee-t/frontend#797 was dealt with, this problem would go away, because then there would be a clear request and error response for @nbiton's MEFE to act on.
The text was updated successfully, but these errors were encountered: