Hi, I keep getting "Failed to send response because lambda function us disconnected", together with a lambda timeout error, the timeout is 10s. This happens randomly it seems. Then afterwards, I get "The security Token included in the request is expired" but then it it works a few minutes later. I get these errors but in the background, the operation completes somehow. EG if I write to a dynamodb table, I get the errors above, (disconnected, timeout, security token) but when I check the table. The data has been written?? I had recently updated to the latest sst version then when these issues cropped up, I downgraded to my original version. But still I got these issues. Another side effect is that, lambdas are invoked twice. For instance, sending an sms or an email, I receive two emails and two sms...

So the issue here is that the lambda in AWS is invoked, forwarded to your local machine, code is executed but for some reason not able to be sent back through

Do you need these logs?

Yeah so in your lambda functions section in AWS console there hsould be a function named something like <stage>-<app>-debug-stack-Resource

Here's the log...

Just following up on this one, did we have a chance to look at this for you @mkarsene?

Hello friends, I just wanted to mention im having the exact same issue, after I upgraded sst form

0.44.0

to

0.54.4

.

what region are you using jacoby?

@thdxr n. virginia

Ok I'm going to have to add some more diagnostics to see if I can get to the bottom of it. From what I'm aware of the only thing that happens between those two lines is connecting to the websocket server

i have an api + lambda setup as showed here. Ive also noticed after running

sst start

, and getting

Debug session started. Listening for requests...

, when i try to call my api, im getting 500s. Lambda logs show timeouts:

@Jay No. Still have the issue regardless of version. Now migrating to serverless framework as I am on a tight schedule and this issue is slowing things down too much. Atleast there I can deploy individual lambdas quickly after every change. Its not live lambda but its quicker than sst right now... hopefully you have better luck.

Yeah we are taking a look into this.

@Jacoby does downgrading fix the problem

@thdxr yes, i downgraded to

0.53.4

and all issues disappeared.

Can you run latest with --verbose and send me the log from start to the listening for messages line

Sorry for not responding, im actually on my vacation 😄. Anyways, yes, im on windows, thanks for the fix, will upgrade shortly. You are the best 💪 .

Awesome!