- Extended flow interpreted as leak risk
- Critical alert unacknowledged in app
- High-pressure anomaly threshold exceeded
Problem Description
Flo automatically shuts off water when it detects critical risk patterns. Users may experience repeated shutoffs during normal activity such as irrigation or long fixture runs. This usually means alert thresholds, usage patterns, or unresolved critical alerts need tuning and validation.
Symptoms
- Water shuts off during normal use
- Recurring shutoff alerts in app
- Irrigation triggers protective cutoff
- Manual reopen works then re-shuts
- No visible leak found
- Family reports intermittent water loss
Recognize these? Here's what usually causes it.
Common Causes
- Extended flow interpreted as leak risk
- Critical alert unacknowledged in app
- High-pressure anomaly threshold exceeded
- Device still in learning/adjustment phase
- Microleak test conflict with active fixtures
- Incorrect home usage profile assumptions
Most fixes happen in the first 3 steps.
Do not permanently disable automatic shutoff just to silence alerts. Tune thresholds instead, or you lose the core protection benefit.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Open root alert details
In the Flo app, review the exact alert that triggered shutoff instead of only reopening water. Shutoffs are normally tied to a specific critical condition such as extended water use, pressure anomaly, or suspected leak. Correcting the root trigger is required to stop repeat events.
Check household usage patterns
Identify regular activities that mimic leak signatures, such as long irrigation zones, pool fill, or high-flow cleaning cycles. Compare these times to alert history. If patterns match, adjust usage strategy and alert settings so expected high-use windows are not treated as unattended leak events.
Run controlled plumbing check
Perform a manual plumbing check when all fixtures are off and no appliances are running water. This helps Flo establish cleaner baseline behavior and reduces false positives from noisy usage periods. If check fails repeatedly, investigate hidden running fixtures or pressure instability.
Tune app protection settings
Use app controls to refine shutoff sensitivity, notifications, and escalation behavior based on your household risk tolerance. Keep automatic protection active but avoid over-triggering on expected consumption patterns. Confirm all household members know how alerts and manual reopen work.
Validate stability over several days
Monitor for three to five days and compare alert frequency before and after tuning. If unexpected shutoffs continue with no physical leak evidence, escalate with logs and pressure history for deeper support review and potential hardware diagnostics.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Schedule irrigation and other long-flow tasks in predictable windows and mark them in household documentation so alert reviews are faster.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Extended flow interpreted as leak risk
- Critical alert unacknowledged in app
- High-pressure anomaly threshold exceeded
- Device still in learning/adjustment phase
- Microleak test conflict with active fixtures
Before you go — try one of these (they fix most cases).
Need More Help? Flo by Moen Support
Note: The contact information below connects you directly to Flo by Moen's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.






