Quick answer

A sprinkler system that finishes all zones and immediately starts again usually has multiple program start times or overlapping active programs. One start time launches every station assigned to that program; it is not a separate start time for each zone.

This guide also answers
sprinkler system runs twicesprinkler timer repeats the whole cycleirrigation program starts again after finishing
Residential sprinkler watering a lawn during a repeated irrigation program
A full sequence that repeats usually points to another program start, not a valve that reopened by itself.

Match the pattern before opening anything

Possible causeBest clueFirst check
Extra program start timesFull sequence repeats in the same orderSet unused start times to OFF
Overlapping A/B/C programsSecond run starts at a different programmed timeReview every active program
Cycle-and-soak featureZones pause and resume in segmentsCheck whether cycling is intentionally enabled
Smart schedule plus fixed scheduleApp shows two schedule typesReview calendar and automation rules

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.

The entire station sequence repeats in the same order

What it meansA second program start time is the leading explanation.

Do nextAudit every start time in every active program.

Only one station repeats

What it meansThat station may have runtime in more than one program or a smart-zone schedule.

Do nextCompare its assignments and history.

The second cycle starts immediately after the first

What it meansProgram stacking can make overlapping starts appear continuous.

Do nextCompare scheduled start times with total program duration.

Short repeats are separated by soak pauses

What it meansCycle-and-soak may be intentional.

Do nextCheck whether the total planned runtime is merely divided into segments.

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

    Write down all start times

    Open Programs A, B, and C and record every enabled start time; do not confuse start-time numbers with station numbers.

    IF YES / NORMALOnly one intended start remains for each program.

    IF NO / ABNORMALAny extra enabled start can launch the full program again.

  2. 02

    Calculate the program end time

    Add station runtimes and soak pauses to the first start time.

    IF YES / NORMALA later event outside that window is a separate start.

    IF NO / ABNORMALAn overlapping start may be stacked until the first program finishes.

  3. 03

    Check individual station assignments

    Find whether the repeated station has nonzero runtime in another active program.

    IF YES / NORMALEach intended station appears only where expected.

    IF NO / ABNORMALRemove only the unintended assignment, not the whole schedule.

  4. 04

    Inspect history before resetting

    For smart controllers, compare app history, local manual commands, and weather adjustments.

    IF YES / NORMALHistory names the initiating program or feature.

    IF NO / ABNORMALNo recorded second command raises wiring, valve, or platform-specific investigation.

Numbers worth measuring

Program durationSum of station runtimes plus programmed soak delays

Use it to distinguish a stacked start from a mysterious immediate repeat.

Values are diagnostic references, not universal pass/fail limits. Confirm the specification for the exact controller, valve, solenoid, nozzle, and local installation.

Common fixes that waste time

Setting Start Time 2 for Station 2

On program-based controllers, start times usually launch the whole program, not matching station numbers.

Factory-resetting first

It erases the schedule evidence needed to identify the duplicate.

Calling cycle-and-soak a duplicate run

Segmented watering is intentional when total runtime is divided by soak intervals.

Worked diagnostic example

How the evidence changes the repair

Four zones completed at 5:42 a.m. and immediately began again.

  • Program A started at 5:00 and totaled 42 minutes.
  • A second Program A start was enabled for 5:30.
  • The controller stacked the overlapping command until the first sequence ended.
Conclusion

The 5:42 restart was not random. Total-duration arithmetic exposed a 5:30 start hidden behind program stacking; disabling that extra start removed the repeat.

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
Write down every enabled start time in every program, then observe one day.

Pass: The system begins only at the intended time.

If not: A second program, smart schedule, or external command remains active.

02
Compare actual zone order with the program list.

Pass: A single sequence completes once.

If not: Station run times in another program identify the duplicate.

03
Check history or controller display after the extra run would normally occur.

Pass: No second start is recorded.

If not: Use the recorded program or command source rather than resetting blindly.

Check these in order

  1. 01

    Write down the exact repeat pattern

    A full sequence restarting suggests another start time. One zone pulsing in segments may be intentional cycle-and-soak rather than duplicate programming.

  2. 02

    Understand start time versus runtime

    A start time begins the program. Each station runtime then determines how long its zone operates. Most homes need one start time for each intended full program cycle.

  3. 03

    Review all start-time slots

    Controllers often allow several start times per program. Set unused slots to OFF rather than 00:00, which some models interpret as midnight.

  4. 04

    Check every program and app schedule

    Review Programs A, B, and C plus smart, fixed, seasonal, and temporary schedules. Disable only confirmed duplicates and preserve intentional drip or slope cycles.

  5. 05

    Watch one scheduled cycle

    After saving changes, observe the next automatic run rather than relying only on a manual test. Confirm the controller does not launch another program later that day.

  • The controller repeats after all schedules are documented and simplified.
  • A shared pump or master valve behaves abnormally during repeats.
  • The controller resets or changes programs after power interruptions.

What homeowners ask about this symptom

Do I need one start time for every sprinkler zone?

Usually no. One program start time runs all stations assigned to that program sequentially. Extra start times repeat the whole program.

Why does the system pause and then water again?

Cycle-and-soak intentionally splits runtime to reduce runoff. Check whether the controller labels the behavior as cycling, soaking, or smart scheduling before disabling it.

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.

Hunter: Sprinklers Not WateringHunter: Automatic Program Not StartingRain Bird: ESP-Me Repeats WateringRain Bird: Programming Irrigation Controllers
Published and last reviewed: August 28, 2026