# Cron-plus: track connections on schedule list move

**URL:** <https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943>\
**Category:** General\
**Created:** [31 August 2023 10:50 UTC](https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943 "2023-08-31T10:50:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [31 August 2023 10:50 UTC](https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943/1 "2023-08-31T10:50:17Z")

</div>

Hi There!

I think I found an inconsistency in cron-plus compared to switch node and I'm not sure whether it's desired or not.

If I have multiple outputs in a switch and I move the conditions around in the list:

![Screen Shot 2023-08-31 at 12.40.50](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/b/5b0db6a29a0fdeae5d797357edb91a295aa26ab9.png)

the outputs will be "sticky", i.e. connections are maintained as they are. Moving 3 above 2 in the above would cause crossed wires - visually.

If I do the same in the cron-plus node:

![Screen Shot 2023-08-31 at 12.44.23](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/e/0e46b519c7a9f34a4ab24ebfb4cbe06c332b4d24.png)

If I move schedule2 above schedule1 then the node that was connected to schedule1 will then be connected to schedule2 and conversely: the node that was connected to schedule2 will be connected to schedule1.

That's confusing but visual since after moving the schedules around, the wires visually looked the same - swapping two schedules should have caused cross wires.

Is that intended?

Cheers!

---

<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:** [31 August 2023 10:52 UTC](https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943/2 "2023-08-31T10:52:55Z")

</div>

> [@gregorius](#):
>
> That's confusing but visual since after moving the schedules around, the wires visually looked the same - swapping two schedules should have caused cross wires.

Not intended - more like an oversight 👼

If you could please [raise an issue](https://github.com/Steve-Mcl/node-red-contrib-cron-plus/issues), I will look at it.

Thanks.

---

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [31 August 2023 11:23 UTC](https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943/3 "2023-08-31T11:23:34Z")

</div>

> [@Steve-Mcl](#):
>
> If you could please [raise an issue](https://github.com/Steve-Mcl/node-red-contrib-cron-plus/issues)

ok done - [Cron-plus: track connections on schedule list move · Issue #67 · Steve-Mcl/node-red-contrib-cron-plus · GitHub](https://github.com/Steve-Mcl/node-red-contrib-cron-plus/issues/67)

Cheers!

---

<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 2023 11:23 UTC](https://discourse.nodered.org/t/cron-plus-track-connections-on-schedule-list-move/80943/4 "2023-10-30T11:23:59Z")

</div>

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