# Issue with cron-plus

**URL:** <https://discourse.nodered.org/t/issue-with-cron-plus/92883>\
**Category:** General\
**Created:** [3 November 2024 15:52 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883 "2024-11-03T15:52:28Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [3 November 2024 15:52 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/1 "2024-11-03T15:52:28Z")

</div>

Something happened with cron-plus after the seasonal time change; although it never happened after previous time changes. Normally my next schedule should be the Golden-Sunset (hour before sunset) pending. However, it's jumped over 2 schedules Golden-Sunset & Sunset to the Night schedule that occurs at midnight for the next day 4-Nov.

The PC that the server is running has the correct date and time for the time change. I've restarted the server (which appears to be displaying the correct time and date for events), re-launched the editor, but it still shows the night schedule pending.  
Is there a way to force cron-plus back to the correct pending schedule Golden-Sunset?

---

<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:** [3 November 2024 16:11 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/2 "2024-11-03T16:11:57Z")

</div>

Can you export and share the Cron node. Also, share screenshots of the node config and the nodes status text. Lastly, if there are any dynamic schedules, export those using export-all topic or screenshot the dynamic schedules.

As for forcing - a redeploy or restart of node-red would (should be enough) however not of that should be necessary since It should have detected the time change and rescheduled accordingly (automatically)

---

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [3 November 2024 16:37 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/3 "2024-11-03T16:37:12Z")

</div>

As mentioned this is the first time the this issue occurred with the time change.

I copied & pasted the node did a deploy of the pasted node; it still shows the wrong pending schedule. I've already tried restarting the server and no change.

Also, tried Restart Flows; same result.

---

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [3 November 2024 16:49 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/4 "2024-11-03T16:49:50Z")

</div>

Here's the specific cron-plus node (attached)  
[cron.plus.txt](https://discourse.nodered.org/uploads/short-url/5eLP59ED4Wmd6erIK7Akf4wCpr2.txt) (4.8 KB)

What's interesting, the skipped schedules are both solar-events.

UPDATE: Tried restarting the node-red server PC; did not make a difference; cron-plus is still skipping the solar events.

---

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [3 November 2024 17:33 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/5 "2024-11-03T17:33:42Z")

</div>

Additional Information.

Had another cron-plus node disabled in another flow; it had a sunrise/sunset solar event.  
When enabled and deployed it displayed the correct sunset pending event.

Seems to suggest there's maybe something corrupted in the subject cron-plus node. May need to rebuild a new cron-plus node.

---

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [3 November 2024 20:59 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/6 "2024-11-03T20:59:23Z")

</div>

More information:  
I loaded a saved flows.json file that has the exact same cron-plus node it's has the same pending schedule; skipping 2 solar schedules.

There must be a configuration file that keeps track of node states; maybe the settings file.

Steve you're the cron-plus contributor and presumed creator; is the last state of a cron-plus node kept anywhere that would cause an old copy to return the same results as the current copy; both copies are identical (no configuration change in 2 years)?

---

<div class="post-metadata">

**Author:** ![xytsrm](https://avatars.discourse-cdn.com/v4/letter/x/6de8d8/32.png) [@xytsrm](https://discourse.nodered.org/u/xytsrm)\
**Post date:** [4 November 2024 11:38 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/7 "2024-11-04T11:38:26Z")

</div>

Found the problem.

---

<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:** [4 November 2024 12:55 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/8 "2024-11-04T12:55:47Z")

</div>

Please tell us what it was so that we will know what to do if someone else has a similar issue.

---

<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:** [18 November 2024 12:56 UTC](https://discourse.nodered.org/t/issue-with-cron-plus/92883/9 "2024-11-18T12:56:05Z")

</div>

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