yep most likely it is, there is no way
yep most likely it is, there is no way to throw an exception then?
4 Replies
Yeah I would expect it to throw, are you awaiting it in the client or via ctx.runAction? What value is being returned if it isn’t throwing?
In this case it is a scheduled internal action so I am not awaiting for it. When I get that error in the Dashboard logs the function just stops
That kinda makes sense if it's infra related and external to your code - but this is also supposed to be really rare, is it happening often? Have you tried action retrier for it?
It is happening on a self-hosted istance, inside a "use node" runtime function when there is a really big argument (e.g. a long document from the database). I will start a new thread on this maybe