Open jaekunchoi opened 11 months ago
"Returning" from SQS doesn't "put message back" that's not how SQL-Lambda integration works.
To re-queue message you will need to call boto3
with the specific SQS handling you want.
return
from lambda is only indication to SQS that message was processed successfully and needs to be removed from the queue. So all the data you return there is ignored.
I have a below code that is a custom lambda handler
and above is registered as custom handler with below code
I also have SQS triggering Lambda function. When message is received from Lambda, it doesn't however put the message back into the queue. It therefore does not even retry.
Is there a reason why this is happening?