feat(awslambda,captureAllSettledReasons) : Capture errors individually on sqs partial batch failure #4130
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.
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint
) & (yarn test
).A lambda can receive up to 1000 messages. (if we use a batchWindow), but it can fail because of 10/1000 messages failed. Tools such as Middy (and the
sqs-partial-batch-failure
plugin) allow managing this case by deleting records from the queue individually, so that we don't have to retry a record that has already worked.This PR suggests adding an option to capture all errors coming from a
Promise.allSettled
. ThewrapHandler
will not fail the lambda even if there are errors, because I assume that it will be the middy’s job.