# Is there a way to force a redeploy of all node-red flows in case no changes have been made?
**URL:** https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899
**Category:** General
**Created:** [6 September 2018 07:04 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899 "2018-09-06T07:04:33Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@janvda](https://discourse.nodered.org/u/janvda)
#### Post date: [6 September 2018 07:04 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/1 "2018-09-06T07:04:33Z")
Currently I have a little issue with one of my nodes that is not automatically reconnecting to a service which I can easily fix by redeploying the node-RED flows.
But in order to redeploy with the node-RED editor I first need to make some small cosmetic change (e.g. moving a node) and only then the deploy button becomes enabled.
I agree this is a little extra effort, but it is also not nice if you are using the node-RED project functionality with github versioning as your cosmetic change becomes also visible as a project change which you also don't want. (So after moving the node - I move it back to its original position to assure that the project didn't change).
**So, is there an easy way that I can use to redeploy all my flows in case they are not changed !**
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [6 September 2018 07:36 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/2 "2018-09-06T07:36:19Z")
or alternatively - fix the node so that it reconnects correctly ?
---
### Author:  [@davidcgu](https://discourse.nodered.org/u/davidcgu)
#### Post date: [6 September 2018 08:25 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/3 "2018-09-06T08:25:58Z")
Just move one one mm on place and will allow u to deploy
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [6 September 2018 08:44 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/5 "2018-09-06T08:44:06Z")
The underlying API does support an HTTP request to reload the current flows without deploying anything new. It just isn't exposed in the editor - that's something we could look at doing.
I agree that with version control/projects enabled, the 'nudge a node' technique causes unnecessary changes and churn.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [6 September 2018 09:20 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/6 "2018-09-06T09:20:01Z")
Which node is causing the problem?
---
### Author:  [@janvda](https://discourse.nodered.org/u/janvda)
#### Post date: [6 September 2018 10:08 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/7 "2018-09-06T10:08:52Z")
> [@knolleary](#):
>
> The underlying API does support an HTTP request to reload the current flows without deploying anything new. It just isn't exposed in the editor - that's something we could look at doing.
>
> I agree that with version control/projects enabled, the 'nudge a node' technique causes unnecessary changes and churn.
Thanks for the response.
For me it would be good if it would be possible using the node-RED UI to force the redeploy of all flows even in case no changes are made.... but I admit that it is better to fix the problem node or replace it with something that is reconnecting properly.
---
### Author:  [@janvda](https://discourse.nodered.org/u/janvda)
#### Post date: [6 September 2018 10:14 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/8 "2018-09-06T10:14:18Z")
> [@zenofmud](#):
>
> Which node is causing the problem?
It is [node-red-contrib-slack](https://flows.nodered.org/node/node-red-contrib-slack)
See issue [https://github.com/yayadrian/node-red-slack/issues/15](https://github.com/yayadrian/node-red-slack/issues/15)
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [6 September 2018 10:55 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/9 "2018-09-06T10:55:47Z")
Hmmm, lookl like the author hasn't been active in GitHub for over a year. Have you thought about seeing if one of the other slack nodes might work for you? I see 10 in the flows library.
---
### Author:  [@janvda](https://discourse.nodered.org/u/janvda)
#### Post date: [6 September 2018 13:37 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/10 "2018-09-06T13:37:45Z")
> [@zenofmud](#):
>
> ...Have you thought about seeing if one of the other slack nodes might work for you? I see 10 in the flows library.
Yes, but none of them immediately seemed better to me. Besides the bot functionality, it must also support the functionality to post messages in specific slack channels.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [6 September 2018 19:52 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/11 "2018-09-06T19:52:36Z")
I regularly feel this need also.
However I have found an easy way, which is to enable and disable a debug node, which results in no change to the flow, but node-red thinks it has changed.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [6 September 2018 20:17 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/12 "2018-09-06T20:17:21Z")
> [@Colin](#):
>
> However I have found an easy way, which is to enable and disable a debug node, which results in no change to the flow, but node-red thinks it has changed.
I didn't think that triggered a re-deploy
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [6 September 2018 20:38 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/13 "2018-09-06T20:38:50Z")
> [@cymplecy](#):
>
> didn't think that triggered a re-deploy
It does for me.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [6 September 2018 20:56 UTC](https://discourse.nodered.org/t/is-there-a-way-to-force-a-redeploy-of-all-node-red-flows-in-case-no-changes-have-been-made/2899/14 "2018-09-06T20:56:41Z")
> [@Colin](#):
>
> It does for me.
So it does!
I didn't think it did but just tried out a simple test and it did
YLSNED 🙂
_I knew it changed the colour of the deploy button to red but I hadn't realised that it was really active_