A robot vacuum that keeps getting stuck is almost always meeting the same few obstacles: high thresholds, dark or glossy floors its sensors misread, loose cords and rug tassels, or a gap just tall enough to enter but too low to exit. Fixing the environment resolves most repeat stalls.
Where robots get stuck, and why
Repeat stalls are rarely random. A robot follows a similar path each run, so it tends to fail in the same handful of spots:
- Thresholds and transitions. Most robots climb about 0.8 inch (2 cm). A saddle between rooms, or the lip of a deep-pile rug just above that height, traps them.
- Under low furniture. A sofa or bed with clearance close to the robot’s own height lets it drive in, then wedges it when the floor rises slightly or it turns.
- Dark or glossy floors. Cliff sensors can read a very dark mat or high-gloss tile as a stair edge and stop the robot, or it slips and loses its bearings.
- Cords, cables, and tassels. Loose cables and rug fringe wrap the brush or wheels and halt the drive.
Fix it in order
- Clear the repeat-offender zones. Watch one full run and note where it stops. Tuck away cords, flip up or remove fringed rugs, and move light obstacles before each clean.
- Block low-clearance furniture. If it wedges under one couch, add a low barrier or a no-go zone in the app so it never enters.
- Clean the wheels and main brush. Hair and fiber wound around the brush or a wheel axle make the robot climb poorly and stall. Remove the brush and cut the wrap away.
- Wipe the cliff sensors. Dust on the downward sensors (underside, near the front) causes false stair readings on normal dark floors. Wipe them with a dry cloth.
- Address dark floors directly. If one dark rug always stops it, some apps let you disable cliff detection in mapped areas, or you can relocate the rug. Do not disable cliff sensors globally if you have real stairs.
When it is the robot, not the room
If the robot stalls in open, cleared floor with nothing underfoot, the cause is more likely internal: a worn wheel, a failing sensor, or a navigation fault introduced by a firmware update. A robot that used to cover the space and suddenly cannot, with no change to the room, is showing its own decline rather than a setup problem. Reliability patterns and post-update regressions for each model are recorded on the robot’s record and in the Tracker.
For the underlying question of how much a robot should handle on its own, see robot vacuum autonomy.