So I had a node red flow working in the background and due to some authentication changes, my email node wasn’t able to send any email's for a period of time.
The problem is, I really need to recall those messages, is there any way I can do that?
The email node still says "send failed", I also have a function node before that that has a debug node connected, but, In the debug session I cannot see any logs since the session wasn’t open on my pc.
If you have any suggestions I would really appreciate.
Thanks!
If it states "send failed", then it was never sent - therefore you cannot recall them (and TBH, there is no need to attempt a recall since they were never sent)!
Am i misunderstanding your requirements?
Perhaps you mean you need to attempt to re-send the original emails now the authentication is updated?
The issue is the user ID I was using to send the emails had It's changed password, so from the "send failed" message, I see it as an unsuccessful attempt to send an email.
Are you saying that the message means there never was a trigger to send in the first place?
My objective was, in the case that there was an attempt to send an email but was blocked by the authentication, i want to retrieve that info that was never sent.
No, i am saying if you got the status text "send failed" it was "never sent"
I think you are asking "how can i tell if send fails"? Use the status node pointed at the email node - use a debug node set to show the complete message to understand what the status contains and how you can use it.
I want to retrieve what was failed to send, because what caused the failure wasn’t lack of payload or unwanted information, was simply a change in the authentication.
I've tried the status node but Im not getting any info
For the future, if you want to make sure all emails are guaranteed to sent, you can use @colinl/node-red-guaranteed-delivery, which comes with an example for email, I think.
You need to keep a copy of the input then. I don't know if the node passes that through on failure. You should be able to catch the failure with a catch node.
