I moved recently to Node-red 1.0 and I noticed a difference of behavior in the messages exchange, due to asynchrone vs synchrone implementation.
Here is my use case , I have a node A sending (at high frequency ) messages to node B.
I see now ( with node red 1.0) that when i redeployed my flow (start/stop flow ) the last message sent by A before the redeploy is received by B after redeploy.
If i add in my settings.js the following option : runtimeSyncDelivery: true , I'm coming back to the previous behavior.
My question is : is there a way to flush messages when stopping the flow ?