MQL5 Symbol Trading Hours: How to Check Trading Sessions Before OrderSend

1. What Are MQL5 Symbol Trading Hours?

1.1 Why You Need to Retrieve Trading Hours

When developing automated trading systems, or EAs, in MQL5, controlling when not to trade is just as important as deciding when to trade.

Problems often occur in situations such as:

• When the market is closed, including weekends and holidays
• Immediately after a session change, when liquidity is low
• During rollover, when spreads can widen sharply
• Symbols with restricted hours, such as CFDs and indices

If these conditions are ignored, the following risks can appear:

• TRADE_RETCODE_MARKET_CLOSED error
• Unfavorable execution caused by abnormal spreads
• Wider slippage
• Order rejection and retry loops

1.2 Basic Structure of Symbol Trading Hours

MQL5 trading hours are managed with the following structure:

• Day of week, 0 to 6, Sunday to Saturday
• Session index, from 0 to multiple sessions
• Start time, from
• End time, to

In other words, trading hours are not always a simple one-day, one-time-range model.
A single day can contain multiple trading sessions.

Example:

Because of this structure, you should not rely on a simple time comparison.
You need to check each session individually.

1.3 Main Function Used

Basic function signature:

bool SymbolInfoSessionTrade(
   string           symbol,       // Symbol
   ENUM_DAY_OF_WEEK day_of_week,  // Day of week
   uint             session_index,// Session index
   datetime&        from,         // Start time
   datetime&        to            // End time
);

Key points of this function:

• true: retrieval succeeded
• false: the session does not exist
• from / to: tradable time range for that day

1.4 Common Misunderstandings and Failures

Common beginner mistakes include:

• Controlling trades with fixed hours, such as 9:00 to 17:00
• Confusing server time with local time
• Ignoring day-of-week differences
• Ignoring the possibility of multiple sessions

The especially important points are:

• FX and CFDs can have different trading hours.
• Specifications differ by broker.
• Holidays and exception hours may be managed separately.

1.5 Practical Use Cases

Main use cases:

• Pre-entry checks, confirming that the market is open
• Avoiding abnormal spreads by excluding low-liquidity periods
• Stopping trades around economic releases
• Avoiding rollover, including swap time ranges
• Stabilizing execution quality

The especially important points are:

• Always check before OrderSend.
• Wrap the check in a reusable function instead of embedding it directly in OnTick.
• Combine it with spread and volatility checks.

2. How to Retrieve Symbol Trading Hours in MQL5

2.1 Overall Implementation Flow

Steps

• Get the current server time with TimeCurrent()
• Get the day of week with TimeDayOfWeek()
• Loop through sessions with SymbolInfoSessionTrade()
• Check whether the current time is inside the range

2.2 Minimal Code You Can Copy

bool IsTradingTime(string symbol)
{
   datetime now = TimeCurrent();
   int day = TimeDayOfWeek(now);

   datetime from, to;

   // The maximum number of sessions is usually small, from 0 to a few sessions
   for(int i = 0; i < 10; i++)
   {
      if(!SymbolInfoSessionTrade(symbol, (ENUM_DAY_OF_WEEK)day, i, from, to))
         break;

      // Compare only the time portion
      datetime now_time = now % 86400;
      datetime from_time = from % 86400;
      datetime to_time = to % 86400;

      if(now_time >= from_time && now_time <= to_time)
         return true;
   }

   return false;
}

2.3 Important Implementation Point

Reason

The from and to values returned by SymbolInfoSessionTrade() are
time-based values that do not include a date.

Therefore, you need to convert values into the time in seconds and compare them with:

now % 86400

Note: What Is 86400?

• 1 day = 86400 seconds
• % is the modulo, or remainder, operator
• This extracts only the time portion after removing the date

2.4 EA Integration Example: Check Before OrderSend

if(!IsTradingTime(_Symbol))
{
   Print("Trading stopped because the market is closed");
   return;
}

// Normal entry process
OrderSend(request, result);

2.5 Common Failures and Fixes

Failure 1: Using Local Time

TimeLocal(); // Not OK

This can drift from server time.
Execution timing becomes incorrect.

Fix

TimeCurrent(); // Required

Failure 2: Checking Only One Session

SymbolInfoSessionTrade(..., 0, ...)

This misses multiple sessions.

Fix

for(int i=0; i<10; i++)

Failure 3: Comparing With the Date Included

if(now >= from && now <= to) // Not OK

The judgment will always be shifted.

Fix

now % 86400

Failure 4: Ignoring Weekends and Holidays

• There are no sessions on Saturdays and Sundays
• CFDs can have market holidays

Fix

• If no session can be retrieved, return false

2.6 Practical Extensions for Better Accuracy

Recommended Combinations

• Spread limit, using SymbolInfoDouble(..., SYMBOL_SPREAD)
• Volatility filter, such as ATR
• Slippage tolerance control
• Execution-condition checks

Example: Simple Filter

double spread = SymbolInfoInteger(_Symbol, SYMBOL_SPREAD);

if(spread > 30)
{
   Print("Stopped because the spread is abnormal");
   return;
}

2.7 Difference From Alternatives

Fixed Time Filter

• Advantage: easy to implement
• Disadvantage: cannot handle broker differences

Symbol Trading Hours

• Advantage: handles symbol and broker dependency
• Disadvantage: slightly more complex to implement

3. How Symbol Trading Hours Work Internally

3.1 Why Trading Hours Differ by Symbol

The main reasons are:

• FX: generally 24 hours, but rollover still exists
• Stock CFDs: depend on exchange hours, such as NYSE and NASDAQ
• Index CFDs: have maintenance periods
• Commodities: often tradable only during specific hours

In short, the market’s own specifications are reflected directly.
If the EA uses fixed hours, mismatches will occur.

Important Practical Points

• Even the same EURUSD symbol can differ slightly by broker
• Differences exist among brokers such as XM, ICMarkets, and Exness
• Daylight saving time, or DST, can shift the hours

3.2 Time Standard in MQL5

Differences Among Main Time Functions

• TimeCurrent(): server time, the most important choice
• TimeLocal(): local PC time, not recommended for this check
• TimeTradeServer(): server time, almost the same purpose

Why Use Server Time?

• Execution is based on the server
• Spreads and price updates are based on the server
• Local time can be wrong or shifted

Common Misunderstandings

• Judging by Japan time
• Assuming the VPS time zone controls the result

Both are incorrect.

3.3 The Core of Session Structure

Why Sessions Are Split

• Maintenance periods, when the server is stopped
• Clearing processes, including rollover
• Exchange lunch breaks for stock-related instruments

Concrete Example

• 00:00 to 23:55, FX
• 23:55 to 00:05, maintenance

In this case:

• Session 1: 00:00 to 23:55
• Session 2: none, because there is a gap

Impact on Implementation

• Assuming one session per day is risky
• You must check sessions in a loop

3.4 Relationship With Execution, Spread, and Slippage

Correlation

• Outside trading hours: execution unavailable or rejected
• Session boundary: spreads widen
• Lower liquidity: slippage increases

Practical Importance

Symbol trading hours are not just a time-retrieval feature.
They work as a filter for trade quality.

3.5 Why Fixed Time Filters Are Not Enough

Problems With Fixed Hours

• They shift during daylight saving time
• They ignore differences among symbols
• They cannot accurately handle CFDs and indices

Advantages of Symbol Trading Hours

• Uses the broker definition directly
• Automatically reflects time adjustments, including DST
• Allows accurate control by symbol

3.6 Common Design Mistakes

Typical Patterns

• Making unnecessary trades at night
• Increasing losses around rollover
• Entering when spreads are widened

The Core Problem

• The EA watches time, not market conditions
• Execution conditions are underestimated

3.7 Practical Design Philosophy

Basic Practical Design

• 1. Trading-hours check, required
• 2. Spread control
• 3. Volatility control
• 4. Strategy logic

Priority

1. Is execution possible?
2. Are conditions unfavorable?
3. Are entry conditions met?

If you do not follow this order,
even correct strategy logic can still lose.

4. Symbol Trading Hours vs. Other Methods

• Fixed time filter: turns trading on or off at specified times
• News filter: stops trading based on an economic calendar
• Symbol trading hours: retrieves the actual tradable time for each symbol

4.1 Method Comparison

4.2 Strengths and Weaknesses of Symbol Trading Hours

Strengths

• Fully follows broker specifications
• Handles differences between symbols
• Automatically reflects DST
• Confirms that execution is possible

Weaknesses

• Does not account for economic news
• Does not detect abnormal spreads
• Does not guarantee the edge of the strategy logic

4.3 Difference From Fixed Time Filters

Characteristics of Fixed Time Filters

if(hour >= 9 && hour <= 17)

• Advantage: simple and fast
• Disadvantage: can drift because it depends on broker conditions

Core Difference

• Fixed time filter: the EA decides the time
• Symbol trading hours: the market definition decides the time

Practical Judgment

• Short-term strategy: fixed time filters can also be useful
• Stability-first design: symbol trading hours are required

4.4 Difference From News Filters

Role of News Filters

• Avoiding events such as NFP and CPI
• Handling sudden volatility changes
• Avoiding rapid spread expansion

Limits

• They do not guarantee that trading is possible
• They do not account for broker specifications

4.5 Best Practical Configuration

Recommended Structure

if(!IsTradingTime(_Symbol)) return;

if(IsHighImpactNews()) return;

if(IsSpreadTooWide()) return;

// Entry conditions

Meaning of This Structure

• 1. Is execution possible?
• 2. Is the environment abnormal?
• 3. Is the strategy condition met?

4.6 Common Wrong Choices

Bad Patterns

• Fixed time only: breaks on holidays and DST
• News only: ignores market closures
• Symbol trading hours only: can still trade during abnormal spreads

4.7 Design Criteria

Decision Framework

• Is the market open? Use symbol trading hours
• Is it a risky time? Use news filters
• Does the time match the strategy? Use fixed time filters

Priority

1. Market condition, required
2. Risk avoidance, important
3. Strategy optimization, optional

5. Common Mistakes and Practical Warnings

5.1 Confusing Server Time and Local Time

Bad Example

datetime now = TimeLocal(); // Incorrect

Correct Implementation

datetime now = TimeCurrent(); // Correct

Why This Is a Problem

• Execution is based on server time
• The VPS time zone is irrelevant
• A few hours of drift can make the EA judge the market as always closed

5.2 Checking Only One Session

Bad Example

SymbolInfoSessionTrade(symbol, day, 0, from, to);

Correct Implementation

for(int i=0; i<10; i++)

Why It Matters

• CFDs and indices often have split sessions
• Lunch breaks and maintenance periods divide trading hours
• Some time ranges may be unavailable even on a trading day

5.3 Comparing With the Date Included

Bad Example

if(now >= from && now <= to)

Correct Method

now % 86400

Reason

• from/to are time-only values
• now contains date plus time
  So they cannot be compared directly

5.4 Ignoring Weekends and Holidays

Common Cases

• Saturday and Sunday: no sessions
• Holidays: some symbols stop trading
• CFDs: irregular market holidays can occur

Fix

if(!SymbolInfoSessionTrade(...))
   break;

If even session 0 cannot be retrieved, trading is not available.

5.5 Ignoring Spread and Liquidity

Problem Examples

• Entering immediately after rollover
• Spread above 50 points
• Execution delay

Fix

double spread = SymbolInfoInteger(_Symbol, SYMBOL_SPREAD);

if(spread > 30)
   return;

Why It Matters

• The market can be unstable even inside trading hours
• Low liquidity can cause unfavorable fills

5.6 Not Checking Immediately Before OrderSend

Bad Design

• Checking only at the beginning of OnTick
  Conditions can change a few seconds later

Correct Design

// Immediately before entry
if(!IsTradingTime(_Symbol)) return;

OrderSend(...);

Reason

• State changes at session boundaries
• Execution can become unavailable within seconds

5.7 Ignoring Exceptions: DST and Broker Differences

Typical Examples

• A one-hour shift during daylight saving time
• Different hours for the same symbol
• Unusual sessions on specific dates

Fix

• Verify with the Strategy Tester
• Confirm with log output

Print("from:", from, " to:", to);

5.8 Practical Checklist

Checklist

• TimeCurrent() is used
• Sessions are processed in a loop
• Only the time portion is compared
• The check runs immediately before OrderSend
• A spread filter is also used
• Broker differences have been tested

6. Practical Use Cases by Strategy Type

6.1 Scalping

Reason

• Profit of only a few pips is strongly affected by spread
• Low liquidity can immediately turn a trade negative
• Execution delay can be critical

Recommended Structure

if(!IsTradingTime(_Symbol)) return;

if(IsSpreadTooWide()) return;

if(!IsHighLiquidityTime()) return;

// Entry

Note

• Many systems limit trading to London and New York hours
• Skipping Tokyo hours is also common in some designs

6.2 Day Trading

How to Use It

• Allow only high-volatility time ranges
• Avoid rollover
• Stop trading around economic releases

Example

if(!IsTradingTime(_Symbol)) return;

if(IsRollOverTime()) return;

Point

• Symbol trading hours alone are not enough
• Use a news filter together with it

6.3 Swing Trading

How to Use It

• Avoid entries during unfavorable time ranges
• Exclude abnormal spread conditions

Characteristics

• The impact is limited because holding periods are longer
• However, entry quality is still affected

6.4 Grid and Averaging Strategies

Problems

• Adding positions even when trading is unavailable
• Entering during widened spreads
• Expanding floating losses around rollover

Recommended Design

if(!IsTradingTime(_Symbol)) return;

if(IsSpreadTooWide()) return;

if(IsVolatilityAbnormal()) return;

Important Point

• The impact is large because entry frequency is high
• Filter quality is tied directly to survival rate

6.5 News-Avoidance EAs

Structure

if(!IsTradingTime(_Symbol)) return;

if(IsHighImpactNews()) return;

Meaning

• If the market is closed, trading is unavailable
• If the market is unstable, trading is avoided

6.6 Practical Priority

Priority

1. Is trading possible? Use symbol trading hours
2. Are conditions unfavorable? Check spread, slippage, and volatility
3. Are strategy conditions met?

Bad Design

// Entry condition first
if(Signal())
{
   OrderSend();
}

Correct Design

if(!IsTradingTime(_Symbol)) return;

if(IsSpreadTooWide()) return;

if(Signal())
{
   OrderSend();
}

6.7 Practical Optimization Points

Optimization Examples

• Change lot size by time range
• Switch logic by session
• Turn trading on or off based on execution quality

Applied Example

if(IsLondonSession())
   lot = 0.2;
else
   lot = 0.1;

6.8 Practical Summary

Core Idea

• Control market conditions, not just clock time
• Protect execution quality
• Reduce unnecessary trades

7. FAQ

7.1 Are Symbol Trading Hours Required?

Reason

• Prevents market-closed errors
• Avoids abnormal spreads
• Stabilizes execution quality

7.2 Are They Unnecessary Because FX Trades 24 Hours?

Note

• Rollover periods exist
• Weekend closures exist
• Low-liquidity time ranges exist

7.3 Is a Fixed Time Filter Enough?

Difference

• Fixed time: manually defined
• Symbol trading hours: automatically retrieved

7.4 Why Does SymbolInfoSessionTrade Return false?

Main Causes

• The session index exceeds the number of available sessions
• There are no trading hours on that day of the week
• It is a weekend or holiday

7.5 Why Compare With %86400?

Reason

• from/to are time-only values
• now contains date plus time
  So it cannot be compared directly

7.6 Which Is More Important, Trading Hours or Spread Filters?

Order

1. Is trading possible? Time
2. Are conditions good? Spread

7.7 Do I Need to Check on Every OnTick?

Reason

• Market state changes in real time
• Conditions can change within seconds

7.8 Is It Needed in Backtesting?

Note

• If it is not implemented correctly, the EA may overtrade
• Results can drift away from live trading behavior

7.9 Can It Be Used for CFDs and Indices?

Reason

• Trading hours are often limited
• Split sessions are common

7.10 Does It Make Trading Completely Safe?

Additional Elements Needed

• Spread control
• Slippage measures
• Volatility management

8. Summary: Best Practical Implementation

8.1 Minimum Required Structure

Required Structure

• Check tradability with symbol trading hours
• Control spread
• Check immediately before sending the order

Implementation Template

if(!IsTradingTime(_Symbol)) return;

double spread = SymbolInfoInteger(_Symbol, SYMBOL_SPREAD);
if(spread > 30) return;

// Entry conditions
if(Signal())
{
   OrderSend(request, result);
}

8.2 Recommended Practical Structure

Recommended Structure

if(!IsTradingTime(_Symbol)) return;

if(IsHighImpactNews()) return;

if(IsSpreadTooWide()) return;

if(IsVolatilityAbnormal()) return;

if(Signal())
{
   OrderSend(request, result);
}

Meaning

• 1. Is execution possible?
• 2. Is the environment abnormal?
• 3. Is there an edge?

8.3 Common Misunderstandings Revisited

Misunderstandings

• Adding this makes the EA profitable: incorrect
• Time control alone is enough: incorrect

Correct Understanding

• Symbol trading hours: foundation
• Strategy logic: determines win or loss

8.4 The Most Important Practical Point

Core Idea

• Reduce trade count
• Avoid unfavorable execution
• Exclude noisy market conditions

Result

• Lower drawdown
• Improved profit factor, or PF
• Better reproducibility

8.5 Final Design Checklist

Checklist

• SymbolInfoSessionTrade is used correctly
• Sessions are processed in a loop
• TimeCurrent() is used
• Only the time portion is compared with %86400
• The check runs immediately before OrderSend
• Spread control is included
• News and volatility are considered

8.6 Next Practical Actions

Recommended Actions

1. Implement the IsTradingTime function
2. Integrate it into the existing EA
3. Compare backtests with the filter on and off
4. Check drawdown and PF

Evaluation Metrics

• PF, profit factor
• DD, drawdown
• Number of trades
• Win rate

8.7 Final Summary

In One Sentence

• A required filter before entry conditions
• A defense layer that protects execution quality
• A foundation that improves EA reproducibility

With this design as the base,
your EA can move from merely running to being ready for practical operation.