Quick answer

Open the skipped event in Rachio History before editing anything. Rachio can intentionally skip watering because of rainfall thresholds, soil saturation, freezing conditions, wind, a manual skip, disabled zones, or day restrictions. The reason in History determines whether to change settings or leave the water-saving decision alone.

This guide also answers
Rachio skipped watering scheduleRachio Weather Intelligence skipwhy did Rachio not water today

Match the pattern before opening anything

Possible causeBest clueFirst check
Rain SkipRecorded or forecast rain exceeds thresholdOpen the History event
Saturation or Freeze SkipSoil or temperature rule is namedReview Weather Intelligence settings
Manual skipNext event only was removedCheck activity history
Schedule restrictionAllowed days or zones exclude the runReview schedule details

Read the system before replacing a part

Use the observation that most closely matches your yard. Each row changes the next test, so you do not spend an afternoon proving the wrong theory.

History names a Weather Intelligence skip

What it meansThe controller intentionally suppressed the event using a weather trigger.

Do nextRead the specific rain, freeze, wind, or saturation reason before overriding.

The schedule is disabled or the zone is excluded

What it meansThere was no eligible command to run.

Do nextRestore only the intended schedule or zone assignment.

A municipal restriction blocks the selected day

What it meansThe skip is policy logic, not a hardware failure.

Do nextCorrect the address/restriction configuration or choose a permitted day.

Manual Quick Run also fails

What it meansThe problem is no longer only schedule logic.

Do nextUse zone-fault or no-water diagnosis.

Four tests that narrow the fault

Stop as soon as one result gives you a clear boundary. The goal is not to perform every test; it is to eliminate whole groups of causes safely.

  1. 01

    Read history before editing

    Open the skipped event and record its reason, schedule, zones, and expected start time.

    IF YES / NORMALA named skip reason defines the correct setting to inspect.

    IF NO / ABNORMALNo event suggests disabled schedule, wrong day, or connectivity/account context.

  2. 02

    Prove one zone with Quick Run

    Run a short permitted manual test from the app or local control.

    IF YES / NORMALHardware can operate; remain on schedule and Weather Intelligence.

    IF NO / ABNORMALMove to electrical, water, or valve diagnosis.

  3. 03

    Audit schedule eligibility

    Check enabled state, selected zones, start rule, allowed days, and local restrictions.

    IF YES / NORMALThe event is eligible apart from weather logic.

    IF NO / ABNORMALCorrect the one mismatched schedule condition.

  4. 04

    Inspect weather triggers

    Compare the recorded skip with Rain, Wind, Freeze, Saturation, and Seasonal Shift settings that apply.

    IF YES / NORMALThe skip matches an intended conservation rule.

    IF NO / ABNORMALVerify location, weather source, thresholds, and support data before disabling protection.

Common fixes that waste time

Disabling all Weather Intelligence

It hides the actual trigger and removes useful water-saving safeguards.

Replacing a valve after Quick Run succeeds

Manual app success proves that zone can operate.

Judging a skip from the home screen alone

History provides the event-level reason needed for diagnosis.

Worked diagnostic example

How the evidence changes the repair

Rachio skipped a clear morning even though no rain fell at the house.

  • History identified a Rain Skip rather than a station fault.
  • The controller location pin was several miles away after an address change.
  • Correcting location aligned weather data; the next eligible schedule ran normally.
Conclusion

The event log prevented a hardware detour. The weather decision was internally consistent but based on the wrong location input.

Reconstructed teaching case based on documented system behavior. It is not presented as a laboratory test or a repair performed by Sprinkler Fix Lab.

How to confirm the repair actually held

A single successful start can hide an intermittent splice, sticky valve, remaining leak, or scheduling problem. Recreate the original conditions before calling the job finished.

01
Use a short permitted Quick Run to preserve the hardware baseline.

Pass: The original symptom stays absent during the direct test.

If not: Repeat the last isolation step; the fault is incomplete or intermittent.

02
Observe the next eligible schedule and read its event history.

Pass: Automatic behavior and recorded status now match physical watering.

If not: A schedule, sensor, smart feature, master command, or cloud-state issue remains.

03
Confirm location, restrictions, and Weather Intelligence states remain intentional.

Pass: The correction holds under normal time, moisture, load, and network conditions.

If not: Use the first changed condition to locate the remaining intermittent boundary.

Recognize the controller state

Check these in order

  1. 01

    Open History before changing settings

    Find the exact scheduled event and read the recorded skip reason. A generic weather guess is less useful than the controller's own audit trail.

  2. 02

    Compare the skip with local conditions

    Check whether rain actually reached your property and whether the selected weather source represents your area. A nearby storm can differ from conditions at the lawn.

  3. 03

    Understand what the named rule does

    Rain, saturation, freeze, and wind skips protect different conditions. Saturation Skip may cancel rather than postpone the event, so absence of a later make-up run can be intentional.

  4. 04

    Verify zone and calendar eligibility

    Confirm the schedule still includes the intended zones and watering days, and that local restrictions or interval rules do not exclude the date.

  5. 05

    Use a short Quick Run as a hardware check

    If a zone waters during Quick Run, the skipped event was likely logic rather than a failed valve. Adjust thresholds only when repeated history and lawn condition show the setting is wrong.

  • Quick Run also fails to produce water.
  • Weather source or controller location is persistently wrong and cannot be corrected.
  • Local watering restrictions conflict with the desired schedule.

What homeowners ask about this symptom

Will Rachio reschedule every skipped watering?

No. Behavior depends on the skip type. Rachio explains that some events, such as Saturation Skip, can be skipped rather than delayed to a later time.

Is a skipped schedule proof the controller is broken?

No. If History names a weather or manual skip and Quick Run works, the controller is making or following a scheduling decision.

Sources and review notes

General maintenance logic is checked against EPA WaterSense outdoor irrigation guidance. Product controls and disassembly steps vary by model; use the current manufacturer manual for your exact valve, controller, or sprinkler head.

Rachio: Weather IntelligenceRachio: Schedule Types and Skips
Published and last reviewed: August 30, 2026