Breadboard Problems: Why Your Circuit Works, Then Doesn't

A circuit that worked yesterday and doesn't today, with no code changes, is one of the most frustrating things in this hobby — and the breadboard is very often the culprit. The reason it costs people whole evenings is that a bad contact behaves exactly like a bug in your program.

Why breadboard faults are so misleading

When a wire is only mostly connected, your sensor returns plausible-but-wrong readings, or works for a while and then stops. That's the signature of a software bug, so that's where people look. Meanwhile the actual fault is a metal clip that's lost its grip.

Learning to suspect the hardware early is one of the biggest practical differences between someone who's been doing this a while and someone who hasn't.

How a breadboard is actually wired inside

Worth getting straight, because a surprising number of "faults" are just a misunderstanding of the layout:

The long rails down each edge (usually marked with red and blue lines) run lengthways. These are for power and ground.
The main area is connected in short rows across the board — typically five holes per row.
The channel down the middle separates the two halves. Rows on opposite sides are not connected. That gap exists so a chip can straddle it with each leg in its own row.

The gotcha that catches everyone once: on many larger breadboards, the power rails are split in the middle — often marked by a small break in the printed line. Power applied at one end simply doesn't reach the other half. If half your circuit is dead, check this before anything else. The fix is a short jumper bridging the two halves of the rail.

The five ways breadboards actually fail

1. Stretched contacts

Each hole grips a wire with a small springy metal clip. Push something too thick in — a component with heavy legs, solid-core wire that's too fat, a header pin that isn't quite the right size — and that clip is permanently widened. It will never grip a normal jumper properly again.

The maddening part is that the damaged hole looks identical to a good one. If a section of your board has become unreliable, this is usually why, and the practical fix is to stop using that area.

2. Cheap boards with weak clips

The very cheapest breadboards use thin, poorly-tensioned contacts that don't grip well when new and get worse quickly. This is the one place in a starter setup where spending slightly more genuinely pays off, because the failure mode costs you debugging time rather than money.

3. Jumper wires with broken conductors

Wire fails inside the insulation, usually right where it enters the connector, after being bent repeatedly. Outwardly it's perfect. Electrically it's open, or worse, intermittent — connected until something is nudged.

This is the single most common cause of "it worked yesterday". Cheap jumper wire bundles are especially prone to it.

4. Oxidised contacts

On an older board, or one stored somewhere damp, the metal contacts oxidise and the connection becomes resistive rather than clean. Symptoms are voltage drops that make no sense — you measure 5V at the supply and 4.6V two rows away.

5. Too much current

Breadboards are built for signals, not power. The internal contacts are small, and passing significant current through them causes heating, voltage drop, and eventually damage. Motors, LED strips, and anything with a real power draw shouldn't be routed through breadboard rails — give them their own supply and share only a ground reference.

Finding the fault in five minutes

A methodical order beats poking at it hopefully:

The wiggle test. With the circuit running, gently press each jumper in turn. If behaviour changes when you touch one, you've found it. Crude, and it works.
Continuity-test every jumper wire with a multimeter, off the board. Bad wires are common enough that this is worth doing to a whole bundle in one go — and then throwing the failures away rather than putting them back.
Measure voltage at the far end of the rail, not at the supply. A meaningful drop points at a bad contact or a split rail.
Move the whole circuit to a different part of the board. If it starts working, the original area has damaged contacts.
Reduce to the smallest circuit that fails. Remove components until the problem disappears; the last thing you removed is where to look.

Habits that prevent most of it

Use proper jumper wire, not offcuts of whatever's in the drawer. Solid-core wire of the correct gauge, or purpose-made jumpers.
Never force anything into a hole. If it needs force, it's too thick and you're about to ruin that contact.
Keep leads short. Long, looping wires are easier to snag and pick up more electrical noise.
Power motors and anything current-hungry separately, sharing only ground.
Once a project is working and you want to keep it, move it off the breadboard. Stripboard or a simple soldered board is far more reliable long term — breadboards are for experimenting, not for permanence.

When it isn't the breadboard

If you've been through all of the above and it's still misbehaving, the next most likely culprits are power supply problems (see the Pi power and SD card guide — undervoltage causes bizarre, unrelated-looking symptoms) or a voltage mismatch between parts (covered here).

Gear that helps

A multimeter with a continuity beeper is what turns this from guesswork into a five-minute job. A decent-quality breadboard and a fresh set of jumper wires are worth replacing rather than fighting once they've started failing.