Skip to content
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

DynamoDB errors lose original message #61

Open
bewood opened this issue Oct 25, 2019 · 2 comments
Open

DynamoDB errors lose original message #61

bewood opened this issue Oct 25, 2019 · 2 comments

Comments

@bewood
Copy link

bewood commented Oct 25, 2019

Expected

The error output of a DynamoDB node to add msg.err to existing msg object.

Actual

The error output of a DynamoDB node is a new msg with only msg.err and a new msg._msgid property.

Impact

This causes issues using DynamoDB in an HTTP endpoint flow because it loses the msg.res object. Additionally, mitigations by stashing msg.res in flow context aren't possible because even the msg._msgid is lost.

@thomaszlow
Copy link

I'm facing the same difficulties because of the missing msg object.

@quarfie
Copy link

quarfie commented Nov 2, 2022

This affects all nodes, not just DynamoDB. It is a problem for me, too, as I run these nodes from flows that are exposed as web services. Without the msg.res and msg.req data in the error, it is impossible to send a response to the original http request, so it must time out instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants