Lambda Error Mystery

Question

Firstly, the Lambda code itself has no issue, and executes fine. What I am seeing in the logs is an error that returns very little info on Google searches and is now a complete mystery to me. I have an Email alert scanning logs for "ERROR" and because this mysterious error has that in it, I keep getting emails for it.

2022-02-21T10:11:46.665+00:00	[ERROR] [1645438306665] LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint
2022-02-21T10:11:46.666+00:00	An error occurred while attempting to execute your code.: LambdaException
2022-02-21T10:11:46.678+00:00	terminate called after throwing an instance of 'std::logic_error'
2022-02-21T10:11:46.678+00:00	what(): basic_string::_M_construct null not valid

Some extra info, which may be red herrings, but including them anyway.

Lambda is written in .NET Core
This seemed to start after enabling X-Ray (Possible red herring)
The error shows up around 5 minutes after Lambda inactivity (Possible red herring)

Any help would be greatly appreciated.

Thanks

Answer

I'm not 100% sure but that might be an error from the Lambda service itself. Best advice is to raise a support ticket so they can investigate further.

Answer

I am also having the same issue, on .net core lambda invocations.

2022-03-24T07:00:00.872+03:00	[ERROR] [1648094400871] LAMBDA_RUNTIME Failed to get next invocation. No Response from endpoint

2022-03-24T07:00:00.873+03:00	An error occurred while attempting to execute your code.: LambdaException

2022-03-24T07:00:00.873+03:00	terminate called after throwing an instance of 'std::logic_error'

2022-03-24T07:00:00.873+03:00	what(): basic_string::_M_construct null not valid

Lambda Error Mystery

Relevanter Inhalt