Orders rejected for "market closed" when the market is open
Posted: Fri Oct 30, 2026 12:58 pm
Orders rejected for "market closed" when the market is open
An order bounces with the message "market is closed" at 3pm on a Tuesday. The chart is moving. The spread looks normal. Nothing seems wrong, except the order won't go through.
Usually the cause is a symbol-level trading session setting. Brokers define sessions per instrument, and the definition may contain gaps: a short break for server maintenance, a pause around a thin period, or a hard stop on one specific pair during an event. The quote feed keeps running because it's a separate system from the order gateway.
Sometimes it's a temporary protection. A risk system flips a pair into "close only" or "disabled" for a minute when volatility explodes, and the error message wasn't written with precision.
A scalper hitting this learns nothing from the text, so the practical response is to check the symbol's session table in the specification, then test with a tiny order on another pair. If the other pair works and the first doesn't, the restriction is local.
Support can sometimes provide the session schedule in writing. Nobody enjoys finding out about a hidden break after a stop fails to place.
Which odd rejection message has shown up on a live account, and what turned out to be behind it?
An order bounces with the message "market is closed" at 3pm on a Tuesday. The chart is moving. The spread looks normal. Nothing seems wrong, except the order won't go through.
Usually the cause is a symbol-level trading session setting. Brokers define sessions per instrument, and the definition may contain gaps: a short break for server maintenance, a pause around a thin period, or a hard stop on one specific pair during an event. The quote feed keeps running because it's a separate system from the order gateway.
Sometimes it's a temporary protection. A risk system flips a pair into "close only" or "disabled" for a minute when volatility explodes, and the error message wasn't written with precision.
A scalper hitting this learns nothing from the text, so the practical response is to check the symbol's session table in the specification, then test with a tiny order on another pair. If the other pair works and the first doesn't, the restriction is local.
Support can sometimes provide the session schedule in writing. Nobody enjoys finding out about a hidden break after a stop fails to place.
Which odd rejection message has shown up on a live account, and what turned out to be behind it?