AWS Lambda Silent Crash – A Platform Failure, Not an Application Bug [pdf]

(lyons-den.com)

115 points nonfamous | 1 comments | 15 Jul 25 01:22 UTC | HN request time: 0s | source

Show context

ceejayoz ◴[15 Jul 25 02:42 UTC] No.44567373[source]▶

I saw this come up on /r/aws a few days back.

This response seemed illuminating:

https://www.reddit.com/r/aws/comments/1lxfblk/comment/n2qww9...

> Looking at (this section)[https://will-o.co/gf4St6hrhY.png], it seems like you're trying to queue up an asyncronous task and then return a response. But when a Lambda handler returns a response, that's the end of execution. You can't return an HTTP response and then do more work after that in the same execution; it's just not a capability of the platform. This is documented behavior: "Your function runs until the handler returns a response, exits, or times out". After you return the object with the message, execution will immediately stop even if other tasks had been queued up.

replies(2): >>44567415 #>>44567675 #

mcflubbins ◴[15 Jul 25 02:49 UTC] No.44567415[source]▶

>>44567373 #

If this is the case (it might very well be) I do at least find it odd that no one on AWS' side was able to explain this to them.

replies(6): >>44567446 #>>44567457 #>>44567464 #>>44567509 #>>44567669 #>>44569284 #

1. arpinum ◴[15 Jul 25 09:00 UTC] No.44569284[source]▶

>>44567415 #

They did, he has writings elsewhere where he says AWS told him it was an application code problem. The sub-title of this screed also says it.

This person should not be trusted to accurately recount a story, I would be sceptical of any claim in the doc.

↑