Two Systems Only Fail When They Run Together (Decision Tree)
Why this matters
Each system tests perfect on its own. Run them at the same time and one or both misbehave. This is the fault that makes a customer sound crazy and a tech look worse, because you keep proving each unit is fine and the complaint keeps coming back. The cause is not a bad part in either system. It is contention: two loads drawing on one resource that was fine for either alone and cannot serve both at once. Once you see it as a shared-resource problem instead of a component problem, the diagnosis and the fix both fall into place, and the parts you were about to swap stay in the truck.
Start here: co-running can create a hazard, not just a fault
Reproducing this fault means running both systems together, and that combination is sometimes the hazard itself. Two gas appliances exhausting at once in a tight house can backdraft. Two heavy electrical loads on a marginal circuit or service can overheat conductors before a breaker reacts. Two water systems can cross-connect. Before you deliberately run both, make sure the combined condition is safe to create, and stop immediately if you see heat, a draft reversal, a spark, or a breaker straining. Diagnose the contention, do not sustain a dangerous one.
The signature: fine alone, fail together
Confirm the pattern before you theorize.
- Run system A alone through its full cycle. Note it works.
- Run system B alone through its full cycle. Note it works.
- Run both together and watch for the symptom.
If each is clean solo and the fault appears only in combination, you are looking at contention, not a failed component. That single test reframes the whole job.
Find the shared resource
Two systems that fight are sharing something finite. Name it.
| Domain | The shared resource | What running both does |
|---|---|---|
| Electrical | A circuit, breaker, shared neutral, or service capacity | Combined draw sags voltage or overloads, tripping or browning out one |
| Water supply | Pressure and flow in a common line | Two simultaneous draws starve one; output drops or a device will not fill or fire |
| Hot water | A single heater's recovery | Two demands outrun capacity; one runs cold |
| Venting and combustion air | A common vent or a tight building envelope | Two exhausting at once reverse draft or starve a burner |
| Drainage | One drain or stack serving both | Combined discharge overwhelms it and backs up |
| Shared mechanical | One pump, compressor, or pad serving two loads | Combined demand exceeds what the shared driver can deliver |
The tell that names the resource: the symptom is the resource running short. Low voltage, low pressure, no hot water, a reversed draft, a backup. Trace that shortfall to the thing both systems pull from.
Measure the resource under combined load
Correlation is the lead; the measurement is the proof.
- Measure the shared resource while both systems run at the point of contention: voltage under the combined electrical load, pressure with both draws open, draft with both appliances firing.
- Compare it to what the affected system needs. If the resource drops below the requirement only when both run, contention is confirmed and located.
- Distinguish capacity from interaction. If the numbers show the demands simply add up past what the resource can supply, it is a capacity shortfall. If the two interfere in a way that is more than additive (one system's operation disturbs the other's control or feedback, not just its supply), it is an interaction fault, and you look at how they couple, not just how much they draw.
The fix menu
Contention has three honest fixes, and which one fits depends on the resource.
- Enlarge the resource: a larger circuit or service, a bigger supply line or regulator, added venting or combustion air, a larger drain, more recovery. The right fix when both loads are legitimate and permanent.
- Separate them: give one system its own dedicated resource so they no longer share. Often cleaner than upsizing a shared path.
- Sequence or interlock them: prevent both from running at once with a control that lets one wait. The right fix when simultaneous operation is not actually required and enlarging is impractical.
Swapping a component does not fix contention, because no component failed. Verify by running both systems together after the change and confirming the shared resource now holds.
Recap
- Confirm the pattern: each system clean alone, the fault only in combination.
- Make sure running both together is safe before you reproduce it.
- Name the finite resource they share and measure it under combined load.
- Decide capacity vs interaction, then enlarge, separate, or sequence; do not swap parts on a contention fault.
References
- NFPA 70 (National Electrical Code) on circuit and service capacity and shared neutrals; NFPA 54 on common venting and combustion air
- Trade-standard practice on sizing shared supply, drainage, and mechanical resources for simultaneous demand
- See related: A Newer System Next to Yours Might Be the Cause; The Static Reading Is Fine but It Fails Under Load