Zone Runs On Manual But Not On Schedule: Bypass Vs Normal Decision Tree

Why this matters

A zone that fires when the technician presses Manual at the controller but does not run during the scheduled cycle is one of the most misdiagnosed irrigation calls. The cabling, valve, and solenoid pass the manual test, so the parts side looks healthy. The fault is almost always in the program logic or in a sensor in the bypass chain. Diagnosing this in 15 minutes preserves callback economics; misdiagnosing it sells a customer a valve they did not need.

Symptom presentation

Customer reports a zone (often the same one each time) that "is not coming on." A walk to the controller and pressing Manual fires the zone normally. Returning at the next scheduled start time, the zone does not run. Other zones in the same program may run normally, or the entire program may be skipped. The customer often blames the lawn-care company's last visit; in fact, this fault profile rarely originates with a service visit.

Quick checks

Confirm three things at the controller: the date and time are correct, the active program shows a start time within the next available window, and the zone in question is enabled in that program with a non-zero run time. The single most common cause of "zone does not run on schedule" is a program where the run time for that zone was zeroed out, either accidentally by the homeowner or intentionally last winter and not restored.

Confirm whether the controller is in a Rain Delay state, Off mode, or has an active sensor bypass indication on the display. Photograph the screen.

Confirm whether multiple programs (A, B, C) are configured. A zone enabled in Program A only, with Program A disabled but Program B running, will not fire. Check every program.

Isolation tree

Step one: program logic. Read the active program assignments for the zone. If the zone is disabled in the active program, the diagnosis is configuration, not hardware. Restore the zone's run time, save, and confirm at the next scheduled cycle.

Step two: rain sensor or soil-moisture sensor in the bypass chain. Most controllers have a sensor input that, when triggered, suppresses scheduled cycles but allows Manual operation. If the sensor is wet (rain sensor disc swollen), shorted, or wired in a stuck-active state, scheduled cycles are suppressed while Manual still works. Visually inspect the sensor disc, the sensor housing, and the wires at the controller terminal. Toggle the sensor bypass switch if present and re-test on a scheduled start.

Step three: smart-controller weather skip. Smart and Wi-Fi controllers can suppress cycles based on forecast rain, recent rainfall logged at a local weather station, or a manual configuration like "skip if rain expected." The controller often shows this as a Watering Adjustment percentage or a "Cycle Skipped" log entry. Read the log; the answer is in plain language.

Step four: water budget or seasonal adjust at zero or near-zero percent. A homeowner who used winter shutdown settings and dialed the budget to zero or 10 percent will see Manual still firing the zones normally but scheduled cycles delivering near-zero runtime.

Step five: clock or calendar fault. A 24-hour clock vs 12-hour clock misconfiguration is a classic source of "the program is set for 5 AM but it never runs." A controller set to PM start times when the customer assumed AM will skip the AM window. Confirm AM/PM and verify the next-cycle preview if the controller exposes it.

Step six: hardware failure on the schedule path. Rare, but possible: the program memory has corrupted, the solid-state output for that zone is intermittent (passes manual surge load but fails on the lower scheduled trip), or the master valve interlock is failing only during the scheduled sequence. This is a true hardware fault and requires replacement, but it is at the bottom of the tree because everything above it accounts for 95 percent of callbacks.

Confirming diagnosis

The diagnosis is confirmed when the corrective action (restoring the zone's program assignment, replacing the rain sensor, restoring the seasonal adjust, fixing the AM/PM setting) results in the zone firing on the next scheduled cycle. Witness the next cycle in person or schedule a follow-up window. Do not close the ticket until the scheduled cycle has fired with the technician present or via a verified controller log.

For smart controllers with cloud connectivity, the cycle log is accessible by mobile app and provides direct evidence of cycle start, zone firing, and any skip reason. Pull the log and attach to the work order.

Remediation

For zeroed program assignment: restore the run time, document the prior value and the new value, leave a printed schedule at the controller, and ask the customer to call before adjusting in the future.

For rain sensor stuck or shorted: replace the sensor with a comparable model, restore the sensor input wiring, and re-test. Most rain sensor failures are end-of-life (10 to 15 years for outdoor disc-style sensors); replacement is routine.

For smart-controller weather skip set too aggressively: walk the customer through the app's watering preferences, set the sensitivity to a reasonable threshold, and document the change.

For confirmed controller hardware fault: replace the controller. Document the failure mode and the prior model.

References

• ASABE/ICC 802-2014 Landscape Irrigation Sprinkler and Emitter Standard
• US EPA WaterSense Specification for Weather-Based Irrigation Controllers
• Irrigation Association, Smart Water Application Technologies (SWAT) protocols
• California Department of Water Resources, Model Water Efficient Landscape Ordinance (MWELO) reference for controller requirements
• University of Florida IFAS Extension, AE220, "Field Evaluation of Irrigation Systems for Florida Landscapes"