1 Answer
- Newest
- Most votes
- Most comments
0
Maybe something in the thread itself that doesn't finish somehow?
If this is actually your code, why are you creating a thread?
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks for the response. A query update doubled the amount of time querying the database, which was enough to cause some of the threads to time out. Wasn't the easiest bug to find because it was failing some of the time. We're currently using threading because it's faster than sequential processing and cheaper than several Lambda functions.