What to Do When Timeframes Give Conflicting Signals

D1 is bullish. H1 just turned bearish. Every multi-timeframe guide tells you to align your timeframes before entering — but none of them spend much time on what to actually do the moment they stop agreeing, which happens more often than the clean textbook examples suggest.

This covers the practical side of that moment: why it happens, and a set of decision rules for handling it instead of guessing.

The Scenario

The pattern is always some version of the same thing: a higher timeframe shows one direction, a lower timeframe shows the opposite, and you're left holding two contradictory pieces of information about the same pair at the same moment.

D1 above its MA200, RSI holding over 50, MACD positive — a clean bullish regime by any standard reading. But H1 has just printed a bearish MA crossover, RSI has dropped under 50, and if you only looked at that one chart, you'd assume the pair was rolling over.

Both readings are correct. They're just answering different questions on different time horizons, and the disagreement between them is information, not noise to be resolved by picking whichever one you like better.

Why This Happens

Regime transitions start on the lower timeframe. Every reversal that eventually shows up on D1 had to begin somewhere, and it begins on H1 or H4 first. A conflict between D1 and H1 sometimes really is the early stage of a genuine shift — the lower timeframe hasn't been wrong, it's been early.

Short-term noise doesn't always mean anything. Far more often, the H1 move is a pullback, a session-driven wobble, or a reaction to a data release that fades within a day. The lower timeframe is technically accurate about its own bar-by-bar behaviour, but that behaviour doesn't reflect a change in the broader trend.

The two situations look identical in the moment. This is the actual problem. You cannot tell, at the instant the conflict appears, whether you're watching the start of a genuine reversal or a routine pullback inside a still-intact trend. Both produce the exact same H1 chart. The difference only becomes visible with time or additional confirmation — which is what the decision rules below are for.

Decision Rules for Resolving the Conflict

Default to the higher timeframe until it changes. D1 represents more price history and more participant consensus than H1. When the two disagree, the working assumption should be that D1 is still right and H1 is a shorter-term wobble — until D1 itself gives a reason to think otherwise. This isn't a guarantee; it's a starting bias that's right more often than the reverse.

Wait for confirmation rather than acting on the lower timeframe alone. If H1 is signalling against your D1 bias, the standard response isn't to flip your position — it's to stop opening new trades in the D1 direction until H1 either confirms (recovers back in line with D1) or the higher timeframe itself starts showing signs of change. Acting immediately on every H1 wobble against a D1 trend is one of the more reliable ways to get whipsawed.

Reduce position size rather than picking a side. When the conflict is genuinely ambiguous — you can't yet tell if it's a pullback or a reversal — sizing down is often the better answer than committing fully to either read. A smaller position in the D1 direction, or staying flat until the picture clarifies, both beat treating an unresolved conflict as a confident signal in either direction.

Give the higher timeframe more weight the longer the conflict persists. A one- or two-candle disagreement on H1 is routine. If H4 also starts turning against the D1 bias, and that persists for several sessions, the balance of evidence has shifted — that's no longer noise, that's the lower timeframes converging on a genuine change the D1 hasn't caught up to yet.

Check whether the disagreement is about direction or about timing. Sometimes what looks like a conflict is actually two timeframes agreeing on direction but disagreeing on when to act — D1 bullish, H1 in a normal pullback before resuming. That's not a conflict requiring a decision; it's exactly what a healthy pullback looks like mid-trend.

A Worked Example

EUR/USD, D1 has been in a clear uptrend for five weeks: price above the D1 MA200, RSI holding between 50 and 70, MACD histogram positive. By the usual reading, this is a confirmed bullish regime.

On H1, price pulls back over two sessions. The H1 MA10 crosses below the MA20, RSI on H1 drops to 38, and MACD on H1 turns negative. Read in isolation, the H1 chart looks bearish.

Applying the rules above: the D1 regime hasn't changed — MA200 still holds, RSI is still above 50, MACD is still positive. The H1 signal, on its own, isn't enough to override that. The response isn't to short the pair on the H1 bearish reading; it's to stop looking for new longs until H1 shows signs of recovering, and to watch whether H4 starts agreeing with H1 (which would be the first real warning that this is more than a pullback).

Two sessions later, H1 RSI recovers back above 50, the H1 MA10 recrosses above the MA20, and H4 never joined the bearish move. The conflict resolves in favour of the D1 trend — this was a pullback, not a reversal, and the entry that would have made sense is the H1 recovery back in line with D1, not a premature short into the pullback.

If instead H4 had started printing the same bearish signals as H1, and that alignment held for several sessions while D1 began flattening, the correct read would have shifted — that combination is what a genuine early-stage reversal looks like, as opposed to a routine pullback.

How Scanvey Makes This Visible

Scanvey displays W1, D1, H4, H1, and M15 side by side for every pair, which means a conflict like the one above is visible immediately rather than discovered by switching between charts. Instead of checking D1, then separately checking H1, then trying to remember what D1 showed, you see both states in the same view — and whether H4 is siding with D1 or with H1, which is often the deciding factor in the rules above.

The matrix shows you where the disagreement is; it doesn't resolve it for you. Whether a specific conflict is an early reversal or a routine pullback still requires the kind of judgment described in this article — Scanvey just removes the manual work of noticing the conflict exists in the first place.

Related articles:

See W1, D1, H4, H1 and M15 side by side for every pair with Scanvey — spot timeframe conflicts the moment they appear, refreshed roughly every 15 minutes.

Frequently asked questions

How long should I wait before deciding a conflict is a real reversal rather than a pullback?

There's no fixed number of candles that works universally, but a useful rule is to watch whether the intermediate timeframe (H4, if the conflict is between D1 and H1) starts agreeing with the lower timeframe. A conflict that stays isolated to the lowest timeframe for a few sessions is usually still a pullback; one that spreads upward through H4 is a stronger signal that something has genuinely changed.

Should I ever trade directly against the higher timeframe when there's a conflict?

Occasionally, but it should be the exception rather than the default. Trading against the higher timeframe generally requires more evidence than trading with it — multiple lower timeframes agreeing, a clear structural break, or a fundamental catalyst — not just a single lower-timeframe signal on its own.

Does this apply the same way to crypto as to forex?

The logic is the same, but crypto's faster, less session-bound moves mean conflicts can resolve — in either direction — more quickly than in forex. The core rules (default to the higher timeframe, wait for confirmation, watch whether the conflict spreads to intermediate timeframes) still apply, just on a compressed timeline.