Well nothing, i am just connected to the FAIL and OK node.
A easy fix I found is sending using an inject node an empty message to the HTTP node.
I found out that no message would go to the HTTP node when the gate was closed therefore never retesting the HTTP node to open the gate.
By bypassing the gate and send a message directly to the HTTP node it trips the node to display a error message or not.
I set up the inject node to do this in an interval and whenever the server is back online the message flowed back.
You are missing the whole point. It is up to you to always send a message either to the OK link or to the FAIL link after sending a message to the http node. You have to work out how to do that.
Your easy fix is not a fix, it is overcoming the fact that you have not sent a message to OK or FAIL. At some point your interval inject will come at an unfortunate moment in the operation and will mess things up.
1 Like
For example you could test for the timeout message that you posted earlier and use that to send the FAIL message. However, it is imperative that you make sure you get exactly one message sent to either the OK or the FAIL link after each attempt to send the data.
I understand, the thing is that the system when the gate is closed doesn't arm/ goes to the OK/FAIL without the message going to the HTTP node which it canĀ“t because it's close.
It works once, but once itĀ“s close it cant reopen...by doing the bypass it checks the node, letting it send the OK/fail message.
Do you think it would bring problems? The only thing its doing itĀ“s making empty requests to the node?
Is the debug you showed earlier with the "522 Origin Connection Time-out" message coming from the Complete node? If it is then if you change that debug node to show Complete Message then what does it show?
Looking again I see it is not from the Complete node, however please show the full message coming from the Complete node in the case of the timeout occurring. I believe I know a simple solution but need that information to be sure.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
Answering the first question, the message is comming from the HTTP node, the complete node shows no messages, but the fail does show! one
For what i understood you want the message when the error occurs? when that occurs only the fail node shows...here it goes:
My payload was " " (empty string)
Thank you for this very interesting example!!
Any reason not to use the q-gate node only? Reading the manual, it seems it could be used as well for the "gate" node?
I am trying to avoid two (similar) nodes when one does the job 
No particular reason. I already use both in other areas so I didn't consider that possibility.
Do you mean that error appears from the Catch node? That appears to conflict with what you said in post 19 where you showed that the node returns html indicating a timeout. I think you need to document all the possible error modes and what you see on each output.
