3 Answers
- Newest
- Most votes
- Most comments
0
Hey, it was the timeout thanks, Uri. I think it is pretty unintuitive that there is a default behavior of retrying your API calls for 24 hours for 185 times. What happened is that amazon killed the call after 5 seconds. However, the request was normally processed by lambda and returned a 200 from its side.
answered 2 years ago
0
My experience: I inputed 0 instead of blank in ...Rules> my-rule > Edit rule > Retry attempts - optional then it stopped calling twice.
answered 10 months ago
Relevant content
- Accepted Answerasked a year ago
- asked 7 months ago
- asked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 7 months ago
Hey, I was thinking a similar thing the requests in the example definitely return a 200 (since I record that as well) but they do take some time (like 5-15 seconds) maybe there is some kind of internal timeout? However, that might explain the 2 attempts in a row but not the random times.
API Destinations maximum timeout is 5 seconds. If it takes your backend longer to respond, EventBridge will retry for up to 24 hours.