-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected message handler failure: done is not a function #182
Comments
@geremyCohen - What version of the |
I am using 5.3.0. I tried using the boilerplate from the home page:
And the messages arrive intermittently (vs my vanilla AWS SDK-based prototype.) In the docs, it says "Messages are deleted from the queue once the handler function has completed successfully." but I wasn't clear on what I had to do in the handler to signal a "success" (if anything). |
So how do you manage retries in the newer versions? On previous versions you could run "done(err)" and this will not delete the message from the queue. |
Unable to replicate this issue. Closing due to inactively. If you wish to continue this discussion, we can re-open. |
I'm having the same doubt, how can I signal the success or failure in the handler function? |
@nspragg same issue here version: sqs-consumer:
specifier: ^11.2.0
version: 11.2.0(@aws-sdk/[email protected])` |
When running this snippet:
I can console.log the message, however I get the error:
I am running on Ubuntu 18.04, node 10.16.3.
Any ideas?
The text was updated successfully, but these errors were encountered: