Defender autotask fails with an error "Error: Runtime exited with error: signal: killed"

Support Defender
1

My autotask fails with an error "Error: Runtime exited with error: signal: killed" during a POST call to the API using axios.

Why I can receive this error?

And the strange thing is that locally it works without an error, but in the Defender (remotely) it fails.

1 Like
2

Hi @smak0v -

I'm reading this is typically the result of not enough memory in the Lambda: https://stackoverflow.com/questions/59057934/aws-lambda-error-runtime-exited-with-error-signal-killed

I would recommend reducing memory usage requirements in your Autotask and/or delegating some of the work to a different process.

Hope that's helpful

1 Like
3

Thank you!

It was really a problem with the algorithm and with the memory usage.