# Node-red-contrib-flow-manager -\> flow-manager-nodes-order.json

**URL:** <https://discourse.nodered.org/t/node-red-contrib-flow-manager-flow-manager-nodes-order-json/50434>\
**Category:** General\
**Created:** [31 August 2021 11:25 UTC](https://discourse.nodered.org/t/node-red-contrib-flow-manager-flow-manager-nodes-order-json/50434 "2021-08-31T11:25:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eastling](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/eastling/32/39127_2.png) [@eastling](https://discourse.nodered.org/u/eastling)\
**Post date:** [31 August 2021 11:25 UTC](https://discourse.nodered.org/t/node-red-contrib-flow-manager-flow-manager-nodes-order-json/50434/1 "2021-08-31T11:25:20Z")

</div>

Hi,  
We are using node-red-contrib-flow-manager to split up our flow to make version handling of the flows more manageable.  
However the file "flow-manager-nodes-order.json" generated by the library just contain an array with all nodes in it. This file is causing conflicts all the time for us.  
From the changelog (0.7) of node-red-contrib-flow-manager:

- added file flow-manager-nodes-order.json to keep nodes order, to remain in sync with UI nodes order, and avoid false-positives of "flows are not up to date" in UI.

From the description the description my best guess is that its not necessary to have this file version handled but I can be sure - anybody with tips / knowledge regarding this?

Thanks in advance!

---

<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:** [30 October 2021 11:26 UTC](https://discourse.nodered.org/t/node-red-contrib-flow-manager-flow-manager-nodes-order-json/50434/2 "2021-10-30T11:26:18Z")

</div>

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