Ecovacs

Ecovacs T20 OMNI Not Resuming Cleaning After Charging

Ecovacs T20 OMNI not resuming cleaning after charging? Check AUTO mode, Continuous Cleaning, Do Not Disturb, return alerts and charging status.

Illustration of a robot vacuum docked while a cleaning task remains unfinished
Diagnose before you disassemble

Begin with the quick checks. Stop if a step requires tools or experience you do not have.

If your Ecovacs T20 OMNI is not resuming cleaning after charging, first confirm that the original task was unfinished. A robot resting at the station after a completed run is a different situation from one that returned with rooms still pending. Keep the task record, return time and any alert before starting another clean.

Next, separate three observations: whether the robot reached the station, whether it is charging and whether it resumes the interrupted task. Success at one stage does not establish success at the next. This guide focuses on continuation; docking and charging faults have their own checks.

Choose the next check

What you noticeNext check
Original task was marked completeReview the selected area and cleaning record
Unfinished AUTO task remains at the dockContinuous Cleaning and Do Not Disturb
Robot returned with an alertResolve the specific message first
Robot reached the station but is not chargingUse the charging guide
Return was for mop-pad washingCheck the current station activity
App status cannot be refreshedCheck connection before interpreting the task

1. Confirm the documented conditions

Ecovacs’ Continuous Cleaning guidance says the feature must be enabled and is valid only in AUTO mode. Do Not Disturb prevents it from triggering, as does an alert on return to the charger. The same instructions caution against restarting or factory-resetting the robot after continuation has triggered.

Capture those settings before changing them. If the original run was an area or custom task, do not use that run as proof that AUTO continuation failed. For the next ordinary cleaning task, choose the documented mode and review the relevant settings beforehand.

Keep the comparison simple. Changing the task mode, quiet schedule and map together makes it harder to tell which condition mattered. Note the original configuration and alter only the relevant setting for the next run.

2. Review Do Not Disturb at the return time

Check whether Do Not Disturb was active when the robot returned, including the saved start and end times. A task started outside the quiet period can reach the station later, so the start time alone is not enough to understand the setting.

For a comparison, use a normal cleaning time outside the active quiet period, or adjust the setting if that suits your household. Keep a screenshot showing the configuration. Do not assume that disabling it means the robot should immediately leave; use the current task state and charging indication to understand what is happening.

Illustration of a phone and notebook for recording cleaning settings and return times
Record the task mode, quiet-period settings and return time before changing the setup. Illustrative view.

3. Read any alert before repeating the run

Copy the exact message shown after return. A tank, sink, bag or part-installation warning provides a more specific next step than a general statement that the robot stopped. Address that warning through the matching procedure and record whether it clears.

For water left in the cleaning sink, use the dirty-water recycling guide. For a dust-bag or collection warning, follow the auto-empty checks. Do not bypass a detection mechanism to make the station complete a cycle.

Once the warning is addressed, keep a note of the original task’s status. A new task you start manually is useful for checking ordinary operation, but it does not demonstrate that the earlier interrupted task resumed automatically.

4. Verify charging rather than station proximity

Observe the charging indication and recorded battery state. A robot parked at the station entrance has not shown that it is charging. If the app or robot does not recognize charging, follow the T20 charging guide before assessing continuation.

If it repeatedly fails to enter the station, use the docking troubleshooting guide. Keep the entrance clear and avoid moving the station during an unfinished-task comparison. A return video helps show whether it docks fully or stops short.

5. Distinguish charging from pad washing

During a mopping task, check the station activity shown in the app rather than assuming every return is a low-battery recharge. Ecovacs provides mop-pad cleaning interval settings under Smart Cleaning. If an interval is changed during a run, the new value applies after the next station return, not to the interval already underway.

Record whether the robot is washing pads, charging or displaying a fault. Avoid repeatedly pausing station care simply to see whether it will leave sooner. If the app is Offline and you cannot read current status, use the T20 connection guide first.

When to contact Ecovacs

Contact support if the same unfinished AUTO task pattern recurs with continuation enabled, no active Do Not Disturb, recognized charging and no return alert. Send the cleaning record, mode, settings screenshots, return time and what happened afterward. Do not diagnose a worn battery from a single non-resuming task.

Frequently asked questions

Does this feature apply to every task type?

Ecovacs specifies AUTO mode. Use that condition when assessing whether the feature works as documented.

Should I factory-reset the robot while it is waiting?

Start with the documented conditions and task record. Resetting changes the situation you are trying to assess.

How long should I wait?

This guide does not assume a fixed resume time. Record the charging state and elapsed time, and ask Ecovacs to assess a repeated failure with those details.

Visit the Ecovacs troubleshooting hub for related T20 OMNI guides.

If the issue is an unexpected restart rather than a failure to continue, follow the T20 OMNI unexpected-start guide.

Still having trouble?

Check the model and symptom again

A similar symptom can have a different cause on another model.

Search related problems