feat: return 200 for Bounce collection VersionError #472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Email notifications arrive at our
/emailnotifications
endpoint asynchronously, and processing them involves retrieving documents from the Bounce collection. This means that multiple server instances sometimes attempt to access and modify the same Bounce document concurrently, resulting in Mongoose throwingVersionErrors
. These errors are caught and HTTP 400 is returned, sometimes resulting in false HTTP 400 alarms.Solution
Check if the error is a
VersionError
, and return 200 if it is. The idea here is that we accept the risk ofVersionErrors
as a limitation of our system, and return an OK response since the error is on our end.Other improvements
Tests for the Bounce and Verification controllers were updated with hardcoded numbers for HTTP status codes instead of using the
http-status-codes
package.