# Deploy keeps 'running' - NodeRed HomeAssistant

**URL:** <https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611>\
**Category:** General\
**Tags:** home-assistant\
**Created:** [21 April 2022 18:50 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611 "2022-04-21T18:50:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jroen85](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jroen85/32/60413_2.png) [@Jroen85](https://discourse.nodered.org/u/Jroen85)\
**Post date:** [21 April 2022 18:50 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/1 "2022-04-21T18:50:10Z")

</div>

Hi All!

I have been using NodeRed for a while but suddenly i'm unable to do deployments. After making desired changes to a flow and hitting the deploy button it keeps 'running' and nothing happens.  
Anyone who is able to help out?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 April 2022 19:06 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/2 "2022-04-21T19:06:18Z")

</div>

I dont use HA so can only ask questions in an effort to help you resolve this.

- What version of node-red are you running (check the node-red menu, top-right hamburger menu, version is listed at the bottom of the menu)

- What browser are you using to access node-red editor?

- Can you look in your browsers console (usually accessed via `F12` key or browser menu under "dev tools") - are there any errors?

---

<div class="post-metadata">

**Author:** ![Jroen85](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jroen85/32/60413_2.png) [@Jroen85](https://discourse.nodered.org/u/Jroen85)\
**Post date:** [21 April 2022 19:10 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/3 "2022-04-21T19:10:50Z")

</div>

- NodeRed version is V2.2.2
- I've tried chrome, safari and firefox
- The console only throws one error 'failed to load [http://localhost:1880/vendor/purify.min.js.map”](http://localhost:1880/vendor/purify.min.js.map%E2%80%9D) But that doesn't seem to be of any harm and is showing up on loading NodeRed

Once hitting the deploy the screen turns grey and the icon is showing that its 'running' but never bumps back to the editor becoming available then. Reloading also returns all changed flows back to their old state

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 April 2022 19:37 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/4 "2022-04-21T19:37:25Z")

</div>

Ah, that sounds like whatever you are deploying is crashing node-red and it is being restarted by the HA Docker environment.

I dont know how (you may need to ask on HA forum) but if you know how - please look at the server side (node-red) logs - i bet there are many clues there.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [22 April 2022 02:55 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/5 "2022-04-22T02:55:44Z")

</div>

> [@Jroen85](#):
>
> After making desired changes to a flow and hitting the deploy button it keeps 'running' and nothing happens.

This seems to be a bug in v2.2.2 that was introduced on Apr 4th with the commit for issue #3509 to "Prevent shortcut deploy when deploy button shaded"

It looks like the variable `hasUnusedConfig` is being used outside of the this section around line #333 of `editor-client/src/js/ui/deploy.js`:

```auto
if (!skipValidation) {
    let hasUnknown = false;
    let hasInvalid = false;
    let hasUnusedConfig = false
...
}

```

and then around line # 464 it's referenced in `$ajax.done()` function.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 April 2022 08:28 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/6 "2022-04-22T08:28:34Z")

</div>

> [@shrickus](#):
>
> `hasUnusedConfig`

Yes, that has been resolved in master: [fix out of scope reference of hasUnusedConfig variable by HiroyasuNishiyama · Pull Request #3535 · node-red/node-red · GitHub](https://github.com/node-red/node-red/pull/3535)

However line 464 is after the deployment so this doesnt match up with the OPs statement "Reloading also returns all changed flows back to their old state"

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [23 April 2022 15:01 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/7 "2022-04-23T15:01:29Z")

</div>

> [@Steve-Mcl](#):
>
> Yes, that has been resolved in master

Thanks Steve -- i've pulled the latest and it fixed my instance as well.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 June 2022 15:01 UTC](https://discourse.nodered.org/t/deploy-keeps-running-nodered-homeassistant/61611/8 "2022-06-22T15:01:29Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.