-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
send message error handling #142
Comments
I guess this issue is a duplicate |
I need to find a way to handle this... the output of the sender node contains the result. But there couldcalso be a timeout.... |
I'm not familiar with node-red internals but maybe it's possible to just throw an exception (and let catch node handle it) and skip payload? |
I will try |
fixed in version 8.9.9 |
A message containing the exception and the causing message object is printed using node.error. |
I could add a second output which would be triggered in case of an exception. So the question is if you want to handle the error in the sender on your own or if you would like to abort the whole flow? |
Thank you. Will test it. |
Then I will implement an optional second output |
I'm testing with empty content and unfortunately neither second output nor catch node is triggered. |
That is ok |
But the message was not sent. It's not a normal situation and it would be nice to be able to react. Besides I see that the second output has data even when there are no errors. |
Right now empty content is ignored... no content = nothing to send. The 2nd output should not send anything. I will check that |
@DarkPark I can not reproduce that. On my machine only one output is triggered. Can you please recheck? |
A warning is issued in this case. I don't dare to change that behavior to not break existing bots. |
I'm very sorry but can't reproduce it either. |
Is there a way to handle errors in the Sender Node?
The catch node is not triggered and Sender Node is not producing any payload.
Please advise.
The text was updated successfully, but these errors were encountered: