QualifiedLow risk

Timer resets part-way through timing

The timer starts but resets before it finishes, so it never completes — the delayed action keeps getting cancelled and never happens.

Safety first

A timer that never completes may be masking a fault that keeps interrupting it. Confirm what would happen when it does complete.

Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.

Full detail — causes, the why, and common mistakes.

Likely causes

Ranked from most to least likely.

  1. 1

    Interrupted supply / trigger to the timer

    Most likely

    If the supply or trigger that keeps the timer running drops momentarily, the timer resets.

  2. 2

    Loose connection causing a brief break

    #2

    A loose terminal interrupts the timer just long enough to reset it.

  3. 3

    Upstream contact chattering

    #3

    A chattering relay/contact feeding the timer keeps interrupting it.

  4. 4

    Wrong mode (retriggerable vs not)

    Least likely

    A retriggerable timer being repeatedly triggered restarts each time, never completing.

Reports are saved on this device to reflect what you actually find.

Testing sequence

Work through one test at a time. Expected reading and what each result means.

Test 1 of 3
1

Watch the timer's supply/trigger during a cycle for any momentary drop at the point it resets.

Expected reading

Steady supply/trigger through the whole timing cycle.

If it passes

Supply/trigger steady — check the mode and upstream contacts.

If it fails

A momentary drop is resetting it — trace that interruption.

View all expected readings at once
1. Watch the timer's supply/trigger during a cycle for any momentary drop at the point it resets.
Steady supply/trigger through the whole timing cycle.
2. Wiggle-test connections feeding the timer while watching for a reset.
No reset when connections are disturbed.
3. Check for an upstream chattering contact and confirm the timer mode (retriggerable vs one-shot) suits the use.
Stable upstream contact and a suitable timer mode.

Fault-finding flowchart

The same logic as a decision tree.

  1. 1
    start

    Timer resets mid-cycle

    → step 2
  2. 2
    decision

    Is the supply/trigger steady through the whole cycle?

    Yes→ step 3No→ step 4
  3. 3
    decision

    Connections sound, upstream stable, and mode correct?

    Yes→ step 5No→ step 6
  4. 4
    result

    A momentary drop resets it — trace the interruption.

  5. 5
    result

    Re-verify the supply/trigger path.

  6. 6
    result

    Repair loose connection / fix chattering contact / set correct mode.

Common mistakes apprentices make

  • Not catching a brief supply/trigger drop that resets the timer.
  • Overlooking a loose terminal causing momentary breaks.
  • Missing an upstream chattering contact.
  • Using a retriggerable mode where one-shot is needed.

When to stop & escalate

If an upstream device is chattering due to a supply issue, address that root cause. Confirm the intended timer mode against the control description if unclear.

If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.

Related faults