A Lambda shows a task-timed-out error while calling an API endpoint, but the API endpoint log shows that the response was returned within a millisecond.
0
I build my APIs using AWS API Gateway, Lambda, and RDS. I’m calling APIs inside a Lambda, but sometimes I’m getting a task timed-out error. Why it’s happening? I checked all the things below; what else can I do?
- The Lambda has enough memory to handle the API calls.
- There is no issue with the concurrent request.
- The API returns a response successfully.
- Everything regarding RDS is OK. DB load, CPU credit, etc.
- As all my Lambdas are inside a VPC, there is no issue with the connectivity.
Language
English
asked 6 months ago227 views
1 Answer
- Newest
- Most votes
- Most comments
0
Difficult to say without more information. What I would suggest is to had log messages in your function to check what is taking long time.
Relevant content
- Accepted Answerasked 2 years ago
- asked 3 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Thanks for your comment. I have logs. Below are the steps of the execution.
It's not happening always. Once or twice a day. I assumed that it could be a request throttle due to concurrent requests or the RDS resource limit being exceeded, but nothing happened.
The network is not a 100% reliable medium. It could be that the API responded, but the response never got to the function. What I would recommend is to put a timeout on the API call and retry in case you do not get the answer in time.