You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the event emitter fires a single 'error' type for message errors and queue conection errors. Would be great if those errors are separated in 'error' and 'message_error'. For example if you want to leave the message in the queue because you can't process it at the moment a message_error would be fired.
Also would be nice if a re-poll option is added when polling the queue fires an error.
I can do a pr for that If you are agree.
Thanks
The text was updated successfully, but these errors were encountered:
Hi @pablovilas. This is a duplicate of #16 so I'm going to close, but would be happy to welcome a PR for two separate error events.
error should be an AWS client error processing_error should be an error returned to done for ease of logging
As for re-polling, we already start a new poll on error. If this behaviour isn't working for you, please raise a separate issue for it with an example.
At the moment the event emitter fires a single 'error' type for message errors and queue conection errors. Would be great if those errors are separated in 'error' and 'message_error'. For example if you want to leave the message in the queue because you can't process it at the moment a message_error would be fired.
Also would be nice if a re-poll option is added when polling the queue fires an error.
I can do a pr for that If you are agree.
Thanks
The text was updated successfully, but these errors were encountered: