# Nested packaged subflow not taking config node propery

**URL:** https://discourse.nodered.org/t/nested-packaged-subflow-not-taking-config-node-propery/95160
**Category:** General
**Created:** [5 February 2025 18:46 UTC](https://discourse.nodered.org/t/nested-packaged-subflow-not-taking-config-node-propery/95160 "2025-02-05T18:46:55Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Colin.Smith1205](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@Colin.Smith1205](https://discourse.nodered.org/u/Colin.Smith1205)
#### Post date: [5 February 2025 18:46 UTC](https://discourse.nodered.org/t/nested-packaged-subflow-not-taking-config-node-propery/95160/1 "2025-02-05T18:46:55Z")

</div>

Hello,

For a project I have made some subflows that were packaged following the processes found here: [Packaging a Subflow as a module : Node-RED](https://nodered.org/docs/creating-nodes/subflow-modules) The nodes work as expected, one of the subflow properties that I use is a config node (s7-endpoint [node-red-contrib-s7 (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-s7/)).

The problems come into play when nesting the nodes within a different subflow. The outer subflow uses the same config node as a property, that the packaged node uses but it seems to not pass properly. This only seems to be an issue after the subflow is packaged. I have tested by nesting the original subflow instead of the packaged node and it worked as expected. Any suggestions are appreciated.

Node Red: 4.0.8

---

<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: [6 May 2025 18:47 UTC](https://discourse.nodered.org/t/nested-packaged-subflow-not-taking-config-node-propery/95160/2 "2025-05-06T18:47:27Z")

</div>

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