Here is the C# cBot implementation designed to run headlessly, monitoring the M15 timeframe and pushing alerts to a mobile terminal when liquidity conditions become optimal.
Deploying this script on a VPS against a raw spread feed creates a completely passive filtering system. The bot handles the quantitative gating, ensuring that a push notification only fires when the asset has the momentum to clear transaction costs rapidly. Once the alert hits your phone, you can manually open the chart to check if the current price action aligns with your pre-marked H4 and D1 support or resistance zones before executing the M15 scalp.
FTtrader, a headless screener on a VPS pushing alerts to the phone fits the session roster idea neatly, because the roster becomes code rather than a list someone has to remember. A small addition would be to log every alert that fires outside the allowed pairs for the session, without sending it. After a few weeks that log answers the obvious question: are the excluded pairs actually worse at those hours, or just excluded by habit?
A trader is watching a NZD cross during the quiet Asian hours. A yellow-icon release appears, something like a regional business survey that nobody on the forum would bother mentioning. The number is not extreme. Yet the pair jumps well beyond its usual range for that hour, then hangs there.
The twist is that the size of the reaction had little to do with the importance of the data. It had everything to do with how few orders were around. In thin conditions, a modest amount of buying or selling by those who do follow that survey is enough to move price, because there is not much resting liquidity to absorb it. The same print during the London session would barely register.
This shows up most on crosses and smaller currencies, where participants are fewer and spreads are wider to begin with. A low-impact label describes the average effect across all market conditions. It does not describe how a particular pair behaves at a particular hour.
It also cuts the other way. A big-looking release at a busy hour can be absorbed with little drama, while a minor one in the dead of night produces a spike that retraces when more participants arrive.
The practical takeaway is to look at the pair, the time of day and the usual range, not just the icon color. A quick look back at how a given pair reacted to similar minor releases can be revealing, though the sample is often small.
Do you track minor releases on thin pairs at all, and have any of them turned out to be a regular source of movement for you?