1 Answer
- Newest
- Most votes
- Most comments
0
I'm gonna close this issue out ... seems like the issue was resolved by AWS ... I can't replicate it any more - crossing fingers it was just a temp thing.
answered 2 years ago
Relevant content
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- How can I use a Lambda function to automatically start an AWS Glue job when a crawler run completes?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
In which region are you seeing this? Are you still seeing this delay?
ahh - good point ... yes, seeing this in 'us-east-1' region. And, yes, still seeing the delay here today. It's interesting, the delay is almost EXACTLY 30 minutes -- when I time it. thank you!
What is the timeout of your lambda? Are you logging asynchronously and not awaiting the completion?
yeah, that's a good point - my timeout is set to 10s. Once the log does come through (after up to 30mins), it does show that the lambda fully completed within the 10s timeout though.
I am having the same experience since this morning (April 7 2022, 9AM EST).