This is the right answer. He’s immediately closing the browser after clicking the button. He should wait for a success UI or at least that the resulting network call finishes with success or a failure to retry on. Not lambdas fault, it’s performing as coded.
This wasn't obvious to me just looking at the problem from a distance, but thankfully testing reduces the level of skill required to get something right :)
Comments
Kinda odd behaviour
That's because the author apparently neglected to parse the resulting page to ensure that the submission succeeded.
If you terminate the system right after sending a form there is no guarantee that the data even left the local buffers for the network.
This is the right answer. He’s immediately closing the browser after clicking the button. He should wait for a success UI or at least that the resulting network call finishes with success or a failure to retry on. Not lambdas fault, it’s performing as coded.
Isn't that the point of serverless though?
It wouldn't have worked regardless of what they ran it on, it's the runtime that terminates.
This wasn't obvious to me just looking at the problem from a distance, but thankfully testing reduces the level of skill required to get something right :)