Hi all, I'm reaching out to you today to gather feedback on a potential new feature in NR v5. This new feature is graceful shutdown of flows – providing a way to halt incoming work while allowing in-progress work to complete before fully stopping. Imagine your flow contains an http in => function …

setup-node-red.sh.txt (10,8 Ko) Download the file Open your terminal Go to downloads directory: cd Downloads Run the file: bash ./setup-node-red.sh.txt Enjoy :winking_face_with_tongue:

@gregorius , can your Erlang-Red support this feature? It would provide a quick way to test it. To prevent users from installing it if they are not familiar with it. Huge thanks :heart:

Can you explain the http scenario again please ? To my mind there are two conditions A message has arrived and is in the flow. Today we may close the reply node before the reply is sent. The client gets a broken connection timeout not a 404. With your fix the reply should get sent. A message ar…

[image] GogoVega: @gregorius , can your Erlang-Red support this feature? You mean a graceful shutting down of flows - not really although I do have a clear "stop" that I send to nodes when the flow stops - to handle socket closures, dropping connections, file closures, etc gracefully. I won't…

I made a slight mistake in my explanation. I wanted to give a more telling example... I recall a previous thread discussing an incorrect error code because the endpoint had been removed. If the connection closes between the HTTP in and HTTP response nodes, my functionality will allow the response t…

so a more extreme example - say it takes 5 secs to handle the http request (I did say it was extreme :slight_smile: ) - on a restart currently the flow will break any requests "in-flight" - but will be back up and running almost instantly. With clean shutdown it will handle those inflight but will b…

The user can also choose not to close the HTTP in node; it will close once there are no more pending messages.

I just thought of introducing a fourth step to the sequence. This new step would be the second, and its role would be to trigger a shutdown workflow. Let's take the dashboard as an example. The workflow is as follows: an MQTT node receives data from a sensor, transmits it to the context and to the…

I thought context already got flushed on close

Yes, this was discussed a few years ago… [image] A catch with persistent file stores General What conclusions in particular? This topic has covered a lot of ground - not all of it pertinent. The graceful shutdown design note is related to how a flow can be st…

Node-RED

Node-RED Forum

[Tester Wanted]: Graceful shutdown of flows

Core Development

Paul-Reed 16 November 2025 19:44 11

Yes, this was discussed a few years ago…

Edit - 5 years ago

Topic		Replies	Views
Gracefully stop node-red General	19	1145	22 August 2024
[Feedback Wanted] Flows Sequence Feature Requests	41	582	5 January 2024
Cmd Node-Red auto shutdown General	1	443	23 March 2020
Custom node subscribed to flow restart event General	21	892	24 April 2025
A new type of flow General	38	657	26 September 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

[Tester Wanted]: Graceful shutdown of flows

Related topics