When there is a change that affects a zone’s calculations (e.g., a watering event or change in settings), the “Next Run” and other scheduling displays are not immediately updated; and sometimes they are not updated until the next day.
This morning for example, there was a problem wherein the Crop ET showed as 0 for the foreseeable future. So the Next Run showed as being far into October. A few hours later, you fixed the Crop ET problem at your end so that all the zones now show a reasonable forecasted Crop ET. But the Next Run is still unchanged and shows it as being far into October.
This problem also shows with watering events. Today is Friday. Let’s say a zone’s Next Run is scheduled for Sunday. Today turns out hotter than predicted, so the zone actually runs on Saturday instead of Sunday. But on Saturday morning after the watering, “Next Run” still shows as being Sunday.
In both these cases, I have to drill down to the moisture balance table for each zone to see the true day that a “Next Run” is predicted to happen.
This has been a problem for awhile, but is getting quite aggravating. It is really bad programming practice to have inconsistent scheduling and zone data being displayed at the same time.
Are there any plans for fix this?