Repository navigation
fix: retry Lambda timeouts in the catalog check and reprocess steps - #1948
Merged
Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
mrgrain
approved these changes
Oct 19, 2026
9pace
marked this pull request as ready for review
October 19, 2026 13:41
9pace
enabled auto-merge
October 19, 2026 13:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #713, which added
Lambda.Unknownto theCheck whether catalog needs udpatingretry because that's how a Lambda timeout was reported. Lambd reports timeouts asSandbox.Timedout, a hung S3 read sends the execution to the dead letter queue:{"errorType":"Sandbox.Timedout","errorMessage":"RequestId: ... Error: Task timed out after 60.00 seconds"}Send for reprocessingin the reprocess workflow also needs this. in the last month this timeout happened 3 times, each on an S3 read in the re-ingest functionBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license