# BUG(?) with how subflows handle \`status\`, \`input\` and \`output\` nodes

**URL:** https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794
**Category:** General
**Created:** [22 March 2023 01:01 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794 "2023-03-22T01:01:34Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [22 March 2023 01:01 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/1 "2023-03-22T01:01:34Z")

</div>

# This is a _quirk_ I just noticed.

I am working on a somewhat big subflow.

I am looking at the tab and want to add another output to the number available.  
_At this point in time I am NOT at the top right corner of the tab, which is where these nodes appear when requested._  
So I go there, increment the `output` value and the little _node_ pops onto the screen.  
_I am going to a very different part of the screen to where I am now._  
I select the _node_, press `<ctrl>x` to COPY it and..... the node (expectidly) vanishes.

## **BUT!** That isn't what really happened.

Yes, it did vanish. But rather than being _prepared_ to be pasted else where on the flow:  
the `output` value decremented by one.

So I had to repeat the `increment`: select the node and DRAG it over the tab to the required place.

This also happens with the `status` option and at a very good guess: the `input` one also.

I can kind of understand the mechanics of what is happening.  
But the process is problematic if you want to put the node else where on the tab!

## I tried this too - and it doesn't work!

To try and get around this: I connected the node to ANOTHER one.  
Then `<ctrl>x`.  
Same.

Is it only my machine on which this happens?  
(_Have the gremlins attacked me?_) 😉

Sorry, but it caught me a couple of times, as I didn't notice it at first.  
The above is a better walk through of what happened.  
I scrolled to the other part of the tab. `<ctrl>v`.... NOTHING.

---

<div class="post-metadata">

### Author: ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [22 March 2023 06:56 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/2 "2023-03-22T06:56:30Z")

</div>

> [@Trying\_to\_learn](#):
>
> I select the _node_, press `<ctrl>x` to COPY it and..... the node (expectidly) vanishes.

`<ctrl>x` doesn't `copy` the item. It `cuts` it - but that's just a minor distinction here.  
I can confirm this finding.  
At least, those terminals should come back when pasted again (`<ctrl>v`).  
On my system (v3.0.2) they don't...

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [22 March 2023 08:11 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/3 "2023-03-22T08:11:50Z")

</div>

Ok, copy/paste mixedup.

I was sure they didn't.

But I've been wrong before - and will be again.

# Update:

Just tried with the `status` output.

`<ctrl>x` move to somewhere else. `<ctrl>v` NOTHING.  
The little `tick` disappears and doesn't come back.

Output node:  
Same.  
The `output` value decreases by one when I _cut_ and doesn't come back when I paste.

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [22 March 2023 08:41 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/4 "2023-03-22T08:41:09Z")

</div>

# Suggestion:

As the top row (where those buttons are to add/ the number of outputs, etc) doesn't scroll:  
When you _tick_ one of those to get another output / status output, etc...

## They appears on the screen shown.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [22 March 2023 15:16 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/5 "2023-03-22T15:16:05Z")

</div>

It would be a nice enhancement if the new status or I/O node appeared on the visible area rather than at the top. Perhaps that is not simple to implement.

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 March 2023 07:39 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/6 "2023-03-24T07:39:57Z")

</div>

Well, if you know more than I do and are not prepared to share, what is the benefit of that post?

I SUGGEST a solution so as to not simply complain.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [24 March 2023 07:58 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/7 "2023-03-24T07:58:24Z")

</div>

> [@Trying\_to\_learn](#):
>
> what is the benefit of that post?

Which post?

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 March 2023 08:01 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/8 "2023-03-24T08:01:03Z")

</div>

> [@Colin](#):
>
> Perhaps that is not simple to implement.

😢 😕 ☹

Perhaps.....

Like the word IF....

Do you know or not?  
If you do: SHARE the information.  
Help me learn.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [24 March 2023 08:47 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/9 "2023-03-24T08:47:44Z")

</div>

> [@Trying\_to\_learn](#):
>
> Do you know or not?  
> If you do: SHARE the information.

No, I don't know. I am not a core developer. I would not have said that if I knew.  
I offered an alternative solution, (place the I/O and Status nodes on the visible screen area rather than at the top), but I have no idea whether that is trivial or almost impossible. Hence I indicated that it may not be simple.

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 March 2023 08:50 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/10 "2023-03-24T08:50:42Z")

</div>

> [@Colin](#):
>
> Hence I indicated that it may not be simple.

Well, that is why I am asking.

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [24 March 2023 09:23 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/11 "2023-03-24T09:23:07Z")

</div>

> [@Trying\_to\_learn](#):
>
> As the top row (where those buttons are to add/ the number of outputs, etc) doesn't scroll:  
> When you _tick_ one of those to get another output / status output, etc...
> 
> ## They appears on the screen shown.

That is a very reasonable suggestion and should be straightforward to implement.

I have raised [Feature: include scroll position when placing subflow i/o nodes · Issue #4111 · node-red/node-red · GitHub](https://github.com/node-red/node-red/issues/4111) so it doesn't get forgotten.

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 March 2023 09:37 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/12 "2023-03-24T09:37:52Z")

</div>

{{{{THANK YOU}}}}  
(Ok: this is added to let me post the reply)

---

<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: [23 May 2023 09:38 UTC](https://discourse.nodered.org/t/bug-with-how-subflows-handle-status-input-and-output-nodes/76794/13 "2023-05-23T09:38:33Z")

</div>

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