Why Your Order Block Failed, A Troubleshooting Guide
Order blocks fail often. That isn't a flaw in the concept, it's a reminder that no zone is guaranteed. But repeated failures often come from avoidable mistakes. Use this troubleshooting list.
1. No liquidity sweep. Did price take liquidity before the move that created the block? Blocks without that context are weaker.
2. Weak displacement. Was the move away from the block strong, with large candles and imbalance? A slow drift isn't convincing.
3. Wrong location. Was the block in premium for a buy, or discount for a sell? Location matters.
4. Against the higher-timeframe bias. A bullish block inside a strong bearish trend is a risky bet.
5. Already mitigated. If price has returned to the zone before, it may be used up.
6. Entering without confirmation. Placing a blind limit order at the edge ignores what price does when it arrives.
7. Poor stop placement. A stop inside the zone is often hit by normal wicks.
8. Bad timing. Trading during dead hours or right before news.
9. Over-marking. Too many blocks on the chart means you're guessing.
10. Emotional entry. Boredom, FOMO, or revenge.
How to use the list: after each failed block trade, go through it and tick which items applied. After 20 trades, you'll know your most frequent cause.
Fix that one first, and your results can improve noticeably.
Why Your Order Block Failed, A Troubleshooting Guide
Why Your Order Block Failed, A Troubleshooting Guide
It’s Fairman 
-
PropScalpDesk
- Posts: 521
- Joined: Sat Sep 19, 2026 7:50 pm
Re: Why Your Order Block Failed, A Troubleshooting Guide
Turning this list into journal columns works better than running through it from memory after a loss. Tick the boxes when you take the trade, not after it fails, so you can't rationalise which applied.
It also helps to split it. Items 1 to 5 and 9 are about the zone and can be checked before price arrives; 6, 7, 8 and 10 are execution. If most failures sit in the first group, fix the marking. If they sit in the second, the zones may be fine and the entries leak.
Item 5 needs a definition. I count a touch of the near edge as mitigated, which removed a lot of second-touch trades that used to look good to me.
It also helps to split it. Items 1 to 5 and 9 are about the zone and can be checked before price arrives; 6, 7, 8 and 10 are execution. If most failures sit in the first group, fix the marking. If they sit in the second, the zones may be fine and the entries leak.
Item 5 needs a definition. I count a touch of the near edge as mitigated, which removed a lot of second-touch trades that used to look good to me.
-
FXS Prop Desk
- Posts: 1693
- Joined: Wed Oct 07, 2026 9:52 am
Re: Why Your Order Block Failed, A Troubleshooting Guide
A useful checklist, and point 1 on the missing sweep is probably the most common cause. One item worth adding: the block's location relative to higher-timeframe levels. A 5M bullish block that sits just under a 4H bearish block or a daily resistance is often run straight over, however clean it looks on the lower chart.
Checking the higher-timeframe map before marking lower-timeframe blocks prevents many of these failures. It also helps to note in the journal which item on the list explained each failed block. After 30 or 40 failures, one or two reasons usually dominate.
Checking the higher-timeframe map before marking lower-timeframe blocks prevents many of these failures. It also helps to note in the journal which item on the list explained each failed block. After 30 or 40 failures, one or two reasons usually dominate.
FXS Official Team | The Idea Lab & Strategy
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Why Your Order Block Failed, A Troubleshooting Guide
One problem with ticking the list only after losses is that you never see how often the same boxes apply to winners. If no sweep shows up on 60 percent of failed blocks but also on 55 percent of the ones that worked, it is not your cause, it is just common.
So I fill in the columns PropScalpDesk described on every block trade, win or lose, and compare the two rates after 40 or so. The items worth fixing are the ones with a clear gap, which for me turned out to be items 5 and 8 rather than the sweep.
On item 8, the dead hour that hurt me most was the rollover around 22:00 London. Spreads on some pairs widen to 2 or 3 pips for a few minutes, and a block that would have held gets tagged by the spread rather than by price.
Item 7 also needs a number rather than a feeling. I place the stop beyond the block by the average spread for that hour plus one pip, so it sits wider at night than at the London open.
Has anyone found a cause that is not on the list at all? Mine was entering blocks that formed during a news spike, where the displacement looked strong but the wick barely traded.
So I fill in the columns PropScalpDesk described on every block trade, win or lose, and compare the two rates after 40 or so. The items worth fixing are the ones with a clear gap, which for me turned out to be items 5 and 8 rather than the sweep.
On item 8, the dead hour that hurt me most was the rollover around 22:00 London. Spreads on some pairs widen to 2 or 3 pips for a few minutes, and a block that would have held gets tagged by the spread rather than by price.
Item 7 also needs a number rather than a feeling. I place the stop beyond the block by the average spread for that hour plus one pip, so it sits wider at night than at the London open.
Has anyone found a cause that is not on the list at all? Mine was entering blocks that formed during a news spike, where the displacement looked strong but the wick barely traded.
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Why Your Order Block Failed, A Troubleshooting Guide
Answering my own question from the last reply, the cause I keep finding that is not on the list is a block whose displacement came from a scheduled number. The move away looks perfect, but it was the release repricing the pair, not a participant leaving orders behind.
The chart shows an invented EURUSD M5 example. The last down candle before the 13:30 London CPI release forms a block at 1.0838 to 1.0845, the release candle runs 28 pips to 1.0873, and when price comes back at 15:10 it goes straight through the block to 1.0822.
On a normal block the return tends to stall at the near edge at least briefly. Here there was nothing resting in the zone, because the buying happened in the few seconds of the release, mostly above it.
My rule now is that a block whose displacement starts within five minutes of a tier one release is not marked at all. If price later builds a second displacement from the same area without news, that one can count.
This sits close to item 2 on the list, but strength alone does not catch it. A release candle is usually the strongest candle of the day, which is exactly why it fools the checklist.
The chart shows an invented EURUSD M5 example. The last down candle before the 13:30 London CPI release forms a block at 1.0838 to 1.0845, the release candle runs 28 pips to 1.0873, and when price comes back at 15:10 it goes straight through the block to 1.0822.
On a normal block the return tends to stall at the near edge at least briefly. Here there was nothing resting in the zone, because the buying happened in the few seconds of the release, mostly above it.
My rule now is that a block whose displacement starts within five minutes of a tier one release is not marked at all. If price later builds a second displacement from the same area without news, that one can count.
This sits close to item 2 on the list, but strength alone does not catch it. A release candle is usually the strongest candle of the day, which is exactly why it fools the checklist.
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
Re: Why Your Order Block Failed, A Troubleshooting Guide
Pending orders with an expiration are handled by the server, which uses its own clock and its own rules. A scalper who sets a buy stop to expire in 10 minutes is trusting that the platform converts the time properly.
Things can go wrong. The expiry time might be interpreted in server time while the user thinks in local time. A daylight saving shift can move it by an hour. Some brokers ignore the expiry field for certain order types, or round it to the nearest minute, or hold orders until the end of the day regardless.
Another common surprise is that "good till cancelled" orders survive weekends and rollover, then execute on an open gap at a price far from the original. A pending order placed on Friday and forgotten can fill on a Sunday spike.
A habit that helps is checking the order list at the end of each session and cancelling anything that is no longer part of the plan. For news-time orders, the cleanup matters even more, because a leftover straddle order is likely to trigger at a bad moment.
Testing expiry behavior on a small order with a short window clarifies how the broker interprets the field.
Cancelling stale orders at the end of each session is the safest habit, but an even better one is to set the expiry on every pending order as a matter of routine. A short expiry means a forgotten order disappears by itself, as long as the broker honors the field, which a small test confirms.
Has a forgotten pending order ever filled at a time or price that was a complete surprise?
Things can go wrong. The expiry time might be interpreted in server time while the user thinks in local time. A daylight saving shift can move it by an hour. Some brokers ignore the expiry field for certain order types, or round it to the nearest minute, or hold orders until the end of the day regardless.
Another common surprise is that "good till cancelled" orders survive weekends and rollover, then execute on an open gap at a price far from the original. A pending order placed on Friday and forgotten can fill on a Sunday spike.
A habit that helps is checking the order list at the end of each session and cancelling anything that is no longer part of the plan. For news-time orders, the cleanup matters even more, because a leftover straddle order is likely to trigger at a bad moment.
Testing expiry behavior on a small order with a short window clarifies how the broker interprets the field.
Cancelling stale orders at the end of each session is the safest habit, but an even better one is to set the expiry on every pending order as a matter of routine. A short expiry means a forgotten order disappears by itself, as long as the broker honors the field, which a small test confirms.
Has a forgotten pending order ever filled at a time or price that was a complete surprise?