And How is that returned to the http response, PLEASE EXPLAIN as I am not seeing it. it does return the last call to mqtt in but not the new one.
The http response has already been returned by the time the mqtt in receives its data and the change node has saved it to context, and that is without any delay or latency in the mqtt call.
You are still assuming that the mqtt output from the http-in is triggering an mqtt output that is needed for the http-response. That makes no sense to me as there are loads of timing issues that will potentially cause hard to track down errors. Also the original post makes no mention (unless I missed it) of some other intermediate flow that would orchestrate the mqtt response which would be needed.
If you take your assumption out, you have a more normal situation where the mqtt out is not related to the http-response - maybe it is recording requests for example.
Without further input from the originator of this thread, we cannot know for sure what is actually happening. But from the image shared, there is no indication of any other processes. So either the flow is incorrect because it makes no sense to directly connect an mqtt output to an mqtt input, or my approach will return to the http-request the latest data from the mqtt-in.
No I am stating/asking how, if the http in needs to be returned to the http response node, how does your diagram do that. I am not asking for the OP, I am clearly asking for myself. But you clearly do not want to respond to my question in a responsive manner.
I will leave this here now as it is clearly pointless asking you to respond to my question.