MyAlgoGuru Help
Education Glossary Open the app

Troubleshooting

Start from what you can see on your screen. Each symptom below lists the checks in the order worth doing them, and points at the chapter that explains why.

This page is organised by what you noticed, not by which part of the platform is involved — because when something is wrong you usually cannot tell which part that is.

Work down the checks in order. They are arranged so the earlier ones eliminate the most possibilities, and most of the time you will stop before the end.

My strategy should have traded, and nothing happened

The commonest report, and five different faults share it. Walk them in this order and stop at the first one with no record:

  1. Was the signal raised at all? Look at the source. If there is no new entry there, nothing downstream had anything to receive — and this is the most frequent cause. Check whether your condition truly became true, and whether it needed a bar that had not closed yet.
  2. Was it delivered to this node? The source has a sequence; the node has a position in it. If the sequence advanced and the position did not, delivery is stuck. Every component will report itself healthy, because each one is — it is the link between them that is not.
  3. Did it match a route? A signal that arrived with no configured destination is dropped. It should appear as a recorded drop; if it does, your configuration is the problem, not the strategy.
  4. Did the engine decide not to trade? This is usually not a fault. Outside the trading window, a risk limit reached, no margin, a position already open, the day's trade count used up. Read the recorded reason — it will tell you immediately.
  5. Was an order sent, and what came back? A rejection, an unfilled limit order and a partial fill are three different problems that all look like "no position".
Tip

A risk limit of 0 is a valid setting meaning never trade, and it sits where people expect to put "no limit". If stage four is declining every signal, check your limits before anything else.

Full explanation: The five places a trade can die.

My position does not match my broker's

The broker's book is authoritative — it is held by the entity that actually faces the exchange. Your platform's view is derived from the fills it knows about, so when they disagree, the derived view is what needs correcting.

  • Confirm the read actually succeeded. An empty book means one of three things: you are genuinely flat, the read was refused, or a different account was queried. Only the first is safe to act on.
  • Check for a partial fill. You ordered 300 and 180 filled is the most common cause, and it leaves every downstream number — stop quantity included — sized for a position you do not have.
  • Look for positions nothing claims, including rows the platform cannot name. A holding on a contract your instrument data does not carry will show as unidentified; that usually means the instrument master for that segment is stale rather than that anything is wrong with the position.
  • Reconcile at the open, not at the close. The same mismatch is a question at 09:20 and an emergency at 15:25.

Full explanation: When your engine and your broker disagree.

A price looks wrong, frozen, or zero

  • Check the age of the last update, not whether the feed is connected. A socket can stay open while nothing comes down it, and the last value you received stays on screen looking entirely plausible.
  • One instrument can be frozen while everything else is fine. Aggregate feed health will be green. Check the instrument you are actually trading.
  • A chain cell showing zero is not a price of zero. It means nothing was measured. Any greek, implied volatility or probability computed from it will look exactly as precise as a real one.
  • Check whether the strike has traded today. High open interest with no volume today is a crowd that has already gone home, and a last-traded price from an hour ago is a historical fact rather than a quote.

Full explanation: Implied volatility is a price, not a forecast and Why every screen stayed green.

My stop triggered but I was not filled

A stop-loss with a limit condition becomes a limit order once it triggers, and a limit order can fail to fill in a fast market.

  • In NSE options there is no market-condition stop. SL-M was discontinued for option contracts on 27 September 2021, so every protective order you place in options is a triggered limit order.
  • Setting the limit equal to the trigger is the version most likely to trigger and never fill. Place the limit some distance beyond the trigger — accepting a worse price in exchange for a much better chance of actually exiting.
  • A stop can also gap through. No order type prevents this. If it happened, your loss is larger than the stop implied, and the lesson is about position size rather than about the order.

Full explanation: Stops that are decisions, not hopes.

My order was rejected

Read the broker's reason code first — it is usually specific. The recurring causes:

  • The price is not on a valid tick. A price between the instrument's permitted increments is rejected, not rounded.
  • Quantity above the permitted size for a single exchange order. Large orders have to be split.
  • The segment is closed, even though another segment is open. Commodity and equity hours differ, and a single assumed close time is right for one and wrong for the others.
  • Insufficient margin — and note that short options carry an additional margin requirement on expiry day, so a position that was fine yesterday may not be today.
  • The session has expired. Broker sessions are time-limited, and some are far shorter than a trading day.

My backtest and my statement disagree

Four layers sit between them, and most disagreements are a forgotten layer rather than an error:

  1. Were costs applied? In the backtester they are off by default, with the bill shown beside the gross result. Many arguments end here, with one number gross and the other net.
  2. What slippage was assumed? Zero slippage assumes you always got the quoted price.
  3. Account-level charges — platform fees and any manager share — are levied per account, not per trade, so they never appear in a per-trade view.
  4. Income tax is in no model on this platform.

Full explanation: Why the curve and the statement disagree.

The screen is stuck and nothing loads

If pages hang rather than erroring, and this is affecting everything rather than one feature, it is usually a shared resource being exhausted somewhere behind the scenes rather than anything you did. The distinguishing signs are that it affects every page at once and that nothing reports an error — it simply never finishes.

What is worth doing: note the time, note what you were doing, and report it. What is not worth doing: repeatedly retrying, which adds to the queue that is already the problem.

I cannot find the contract or expiry I want

  • Expiry days have been revised more than once. Read the expiry date from the contract rather than assuming a weekday.
  • Each exchange offers weekly expiry on one benchmark index only since 20 November 2024 — Nifty 50 on NSE, Sensex on BSE. Other indices are monthly. If you are looking for a weekly contract that used to exist, this is why.
  • Past expiries are not uniformly available, and intraday history for expired contracts is patchier than daily history.

Full explanation: Decay through the week, and the expiry-day regime.

Still stuck

Three places to look, depending on what you need:

  • All features — every screen, described in the order the product is organised.
  • Glossary — if you met a term you do not know.
  • A to Z index — if you know the word but not where it lives.

And when you report a problem, these four details save the most time: what you expected, what you saw, the exact time, and the instrument. The time matters more than it sounds — most of the checks above are questions about what was true at a particular moment.