AE appears early in the cycle
The dishwasher starts, fills, then stops quickly with the code.
Start here: Look first for leftover suds, a mis-seated filter, or a door that is not closing evenly.
Direct answer: An LG dishwasher AE code usually means the machine thinks it has a leak, or water has collected in the bottom leak tray. Most of the time the cause is simpler than a failed major part: too much suds, a door not sealing cleanly, a filter or spray arm issue that throws water where it should not go, or a small hose leak underneath.
Most likely: Start with soap and loading mistakes, then check the door gasket area, lower spray arm, filter seating, and the floor under the dishwasher for fresh drips.
AE is a leak-protection warning, not a precise parts diagnosis. Reality check: a single bad wash with the wrong detergent can trip it. Common wrong move: resetting the code over and over without finding where the water came from.
Don’t start with: Do not start by ordering a pump or control part just because the code came back once.
The dishwasher starts, fills, then stops quickly with the code.
Start here: Look first for leftover suds, a mis-seated filter, or a door that is not closing evenly.
It runs for a while, then shuts down after washing begins.
Start here: Check the lower spray arm, loading pattern, and door gasket area for water being thrown toward the front.
You find a wet toe-kick area or damp floor near one front corner.
Start here: Look for door seal leaks, a tilted dishwasher, or a drain hose or sump leak underneath.
The code goes away briefly, then comes back on the next run.
Start here: That usually means there is still active leaking or trapped water in the base pan that has not dried out.
Extra foam can push water past the door and into the base pan, especially if rinse aid is high or dish soap was used by mistake.
Quick check: Open the tub after the code and look for foam, slippery residue, or suds clinging around the bottom and door.
A split or clogged lower spray arm, tall item blocking the arm, or a filter not seated flat can redirect water toward the door seam.
Quick check: Spin the lower spray arm by hand, inspect for cracks, and make sure the filter assembly locks down fully.
Food buildup, a twisted dishwasher door gasket, or a dishwasher that leans slightly forward can let wash water escape at the bottom corners.
Quick check: Wipe the gasket and door lip clean, then look for flattened spots, tears, or a gap at one corner.
A drip from the dishwasher drain hose, sump area, or fill path can collect in the leak tray and trigger AE even if the tub looks normal.
Quick check: Remove the toe-kick if accessible and look for fresh drips, mineral tracks, or wet insulation under the tub.
You want to stop water damage first and separate a one-time suds event from an active leak.
Next move: If the code does not return after the suds are gone, the problem was likely detergent-related rather than a failed part. If the code returns with little or no suds present, keep going and look for where water is escaping.
What to conclude: AE needs an actual source. Suds are common, but repeat trips usually mean water is still getting into the base pan.
Front-edge leaks are common and usually come from spray pattern, loading, or sealing problems you can see without pulling the dishwasher.
Next move: If the next test cycle stays dry at the front edge, the issue was likely spray deflection, debris, or a filter seating problem. If water still shows up at the front corners or the code returns, check leveling and the underside for a true leak.
What to conclude: When water gets thrown toward the door instead of staying in the wash pattern, AE can trip even though the pump and drain system are fine.
A dishwasher that tips slightly forward or has a damaged front seal can leak only during wash action, which makes AE look intermittent.
Next move: If correcting the level or cleaning the seal path stops the leak, you can usually keep the existing parts unless the gasket is damaged. If the front stays dry but AE still returns, the leak is more likely underneath.
Once the easy front causes are ruled out, the next useful move is finding fresh water tracks under the machine instead of guessing at parts.
Next move: If you catch the leak at a hose connection or see a cracked hose, you have a clear repair path. If the base pan keeps getting wet but you cannot see the source, the leak may be from a sump seal, internal hose, or another hidden component that usually requires pulling the dishwasher.
AE can stay active if water remains in the leak tray, so you need one clean retest after drying to confirm the fix.
A good result: If the cycle finishes dry and AE stays gone, you found the cause.
If not: If AE returns with no visible front leak and no obvious hose issue, stop chasing it with random parts and schedule service for a hidden sump or internal leak diagnosis.
What to conclude: One dry test cycle is a good confirmation. A repeat AE after careful checks usually means the leak source is underneath or inside the base where access gets more involved.
Repair Riot may earn a commission from qualifying purchases, at no extra cost to you.
It usually means the dishwasher leak protection has been triggered. That can happen from an actual leak underneath, water escaping at the door, or heavy suds that push water into the base pan.
Yes. Dish soap or too much detergent can create enough foam to force water past the door seal and trip the leak sensor. That is one of the first things worth checking.
Because the source was not fixed or the base area still had water in it. Resetting alone does not solve the leak condition.
No, not usually. More often it is suds, a spray issue, a door sealing problem, or a small hose leak. A pump-related leak is possible, but it is not the first thing to assume.
Not until you know why it tripped. Repeated use can send more water into the base, damage flooring, and make the real leak harder to pinpoint.
That usually means the leak is hidden underneath or only happens during a certain part of the cycle. At that point, drying the base and doing one watched test cycle is reasonable. If you still cannot catch the source, service is the smarter next move.