Automation safety, from the morning checklist to the unexpected fill
A running strategy needs watching in a particular way. What to monitor, when to pause and when to stop, why a kill switch is different from both, how broker session expiry catches people out, a morning checklist, and what to do after a fill you did not expect.
An automated strategy is not a machine you switch on and forget. It is a machine you switch on and watch differently. The watching is lighter than discretionary trading, because the decisions are already made, but it has to be reliable, because the strategy keeps acting on its rule whether or not you are paying attention. This post covers the habits that keep an automated system safe: what to look at, the difference between pausing, stopping and killing, the broker problems behind most incidents, a morning checklist, and the right response to a fill you did not expect.
What to monitor, and what not to
The temptation is to watch the running profit and loss. It is the least useful number on the screen, because it changes every tick and tells you nothing about whether the strategy is working as designed. Watch these instead.
Is it alive? A running strategy should show that it is active, which version it is running, and when it last evaluated its rule. A strategy that has silently stopped evaluating is the most dangerous state, because it looks like a quiet day.
Is it doing what the rule says? The execution log is the record: the signal, the risk check, the size, the order sent, the exit. Read it at least once a day for a few trades and ask whether each step matches the rule as written. Extra trades, missing trades and trades outside the entry window are all signs the rule or its settings need attention.
Is the broker accepting the orders? Rejected orders have reasons: market closed, insufficient margin, quantity below minimum, wrong product type, session expired. A strategy with rejected orders is a strategy that is not in the positions it thinks it is in.
Does live match the test? Over a week, compare the live trades with the paper run or the backtest. Fills a little worse than the test are normal; a different set of trades is not.
Pause, stop and kill switch
These are three different actions, and the difference matters under pressure.
Pause means no new entries, while existing positions continue to be managed by the rule: stops, targets and time exits still run. This is the right action before a scheduled announcement, during a broker problem you expect to clear, or whenever you want to think without the strategy adding to the situation.
Stop means the strategy halts entirely. It does not close anything by itself; the positions it opened are now yours to manage by hand. Use it when the rule is doing something you do not understand, and go straight to the positions afterwards.
Kill switch is the emergency action at the account level: it halts automated activity on an account at once, for the moment when everything must stop and the details can wait. Know in advance what it does and does not close, so that "everything has stopped" is never confused with "everything is flat".
Decide in advance which action fits which situation, and practise each one on a paper account so that the first press is not an emergency.
When to pause
Pause before events you know about and the rule does not: scheduled announcements, expiry days if the rule was never tested through one, the first session after a holiday. Pause when the broker connection looks unwell, when orders are being rejected, or when prices on your screen stop updating. Pause when the day's result reaches a level that makes you want to intervene; pausing is the intervention that does least harm. And pause when you cannot watch at all, unless you have deliberately tested and decided that the strategy may run unattended with its daily loss limit as the only guard.
Broker session expiry
The most common automation incident on Indian markets is not a bad rule. It is a broker session that expired overnight. Many Indian brokers end the connection's session every day and need a fresh login before the open; some renew automatically and tell you only when renewal fails. A strategy whose broker login has lapsed cannot place its first order of the morning, and may sit idle or accumulate signals it cannot act on.
The defence is a habit: know which of your brokers expire daily, log in before the open, and treat a "needs today's login" status as a blocker, not a warning. The same applies to the connection for an MT5 account: if the terminal or the link that carries its prices and orders is down, the strategy is blind.
A morning checklist
Ten minutes before the first market you trade opens:
Broker status. Every account the strategies use shows live or connected, and any daily-login broker has been logged in today.
Prices moving. The symbols the strategies trade are updating, not showing last night's close.
Positions reconciled. The positions the platform shows match what the broker shows, and you know why each one is open.
Strategies in the right state. The ones that should be running are active on the version you intend; the ones that should be paused are paused. Nothing is running that you forgot about.
Calendar. Any scheduled announcement, expiry or holiday today, and a decision about pausing around it.
Limits. The daily loss limit and the maximum entries per day are set, and you know what will happen when they trip.
Write it down and go through it in order. A checklist kept in your head is skipped on exactly the mornings it matters.
After an unexpected fill
Sooner or later a strategy will open or close a position you did not expect. The order of operations is:
Pause the strategy so it does not add to the situation. Do not stop it yet; let it manage the exit if the position is one it opened.
Confirm the position at the broker, not just on the screen. Side, quantity, entry price, and whether a stop is in place and where.
Decide about the position on its own merits. The question is not whether the rule should have done this but whether you want to hold the position now. If not, close it by hand, and check the close went through.
Read the execution log to find out why the fill happened: a signal you did not expect, a condition that evaluated differently from what you assumed, a rejected order followed by a retry, a size calculation that used a different balance.
Fix the cause before resuming. If you cannot explain the fill, do not resume. Run the strategy on paper until you can.
Write it in the journal with a tag. Unexpected fills are the most valuable entries a journal of automated trading contains.
How DalRoti helps
Each running strategy in DalRoti has a Monitor page showing whether it is active, which version is pinned, a heartbeat and the time of the last evaluation, with an execution log that records each signal, risk check, size, order and exit, the broker's orders and the closed trades. Pause stops new entries while exits still run; Stop halts the strategy without closing anything, and the Positions pane has a Close control for everything or by account. Kill switches work per account and per strategy, a daily loss limit stops a strategy when reached, and the Trade copier has its own pause and kill switch.
Notifications cover the situations above: a strategy that needs attention or was paused or stopped is always on; order rejections arrive with the broker's reason; there is a broker-disconnected alert and a morning login reminder at 08:30 IST for daily-login brokers, and the Brokers page shows when an account needs today's login. These can be delivered in-app, by email, by push on the mobile app and, for strategy alerts, by Telegram once linked. For stop-loss protection, a strategy can hold its stop as a broker order, the choice the help centre suggests when your connection may drop, or have DalRoti manage it. LockMe lets you lock an account for a chosen period, closing positions and refusing new orders until the time is up.
Trading involves a high risk of loss. DalRoti is a software tool and does not guarantee any profit. Decide your own risk and position size.
AI Generated