A refused order never reaches the market and does not open a position, and no brokerage is charged on it. The risk is not the refusal itself but what it leaves behind: a strategy with a missing leg, a stop that was never placed, or an exit that did not happen.
Find the reason first
- Open Portfolio → Orders and find the order marked Rejected.
- Tap it. The details sheet shows the status trail, any fills, and the reason in plain words.
- If the reason came from your broker or the exchange, its wording is theirs, so it differs by broker. If it is unclear, check the same order in your broker's own app.
For an algo's order, the algo's card also has a line for the refusal in its activity log, and the algo acts on it by its rules, as described below.
How an order travels
Every order in QuantPower, whether from you, an algo, a signal, a basket, the Scalper, a GTT, a stock SIP, Smart Exit or an AI app's prepared order you confirmed, goes through one path:
- Prepare. QuantPower checks the instrument, the product, the lot size and the tick size.
- Account settings. The segment must be on for your account.
- Risk. The kill switch, the daily loss limit, the maximum orders a day and the ban list are checked. A square-off is never blocked by these.
- Your tap. A manual order must carry your confirmation from the order sheet. It works once, for that exact order, and lasts 60 seconds. Algos and armed signals do not need it: you switched them on.
- Your broker. The order goes to the broker that holds the position, or the one you picked, from your static IP.
- Record. The order and its events are stored and shown to you live.
A refusal at steps 1 to 4 comes from QuantPower, with a reason that names the check. A refusal at step 5 comes from your broker or the exchange.
Refusals from QuantPower's checks
| Reason | What it means | What to do |
|---|---|---|
| Quantity not a whole number of lots, or wrong tick | The order does not fit the contract | Fix the lots; price in steps of the tick size |
| Segment not on | The segment is not enabled for your account | Ask your broker to enable it, then reconnect |
| Kill switch | You stopped trading in that segment until its next session | Wait for the next session. Square-offs still go through |
| Daily loss limit reached | Today's loss reached your limit; new orders are refused | Only closing orders are accepted today |
| Maximum orders a day | The cap you set was reached | Raise it in Algos → M2M if that was not intended |
| In the F&O ban | The stock is in the ban period; only reducing orders are accepted | Reduce or hold; no new positions until it leaves the ban |
| Confirmation expired | More than 60 seconds passed, or the order changed after you confirmed | Confirm again from the order sheet |
| Broker not signed in | The broker's daily session has ended | Sign in again from the Brokers screen |
| Broker activation pending | Your keys are saved, but orders to this broker are not yet switched on | Contact us; nothing is sent until it is active |
| Static IP not available | The route through your static IP is down; the order is held, never sent from another address | Wait and check Orders; see below |
Refusals from your broker or the exchange
| Reason group | What it means | What to do |
|---|---|---|
| Margin | The order needs more margin than is free | Add funds, reduce lots, or place hedge legs first. The margin calculator estimates the need |
| Order type not allowed | The broker or exchange does not accept this type here | Use a limit order. In NSE options, use SL with a limit rather than SL-M |
| Price outside the band | The limit or trigger is too far from the market | Price closer to the last traded price |
| Above the freeze quantity | The order is larger than the exchange accepts in one piece | Split it with an iceberg order |
| Contract | Expired, not yet listed, or restricted by the broker | Choose the current contract |
| Static IP not registered | The broker sees an IP it does not have on record for your API key | Register both static IPs shown on the Brokers screen at your broker |
| Order rate | Orders sent faster than allowed | QuantPower caps each broker connection at 10 orders a second and 250 a minute, lower where the broker sets lower |
| Broker restriction | The broker's risk team has blocked the contract or the account | Ask your broker for the reason |
The guide to order types explains which types each segment accepts.
When an answer is lost
Sometimes the order leaves but the answer does not come back, because a connection dropped. QuantPower never guesses what happened:
- Every order carries a unique key. If the same request is sent again, it can never place twice.
- If the answer is lost, the app asks the server about that key before it tells you anything. It never says "nothing was sent" when it does not know.
- It never retries an order on its own after a lost answer. Check Orders: the order shows there as soon as the broker reports it.
If your static IP route is down, orders are held, not sent from another address. They show as waiting; check Orders when the route is back. Do not place the same order again by hand while one is held, or both may go through.
If one leg of a strategy is refused
A multi-leg position with a missing leg carries a different risk from the one you planned. A short straddle with only the call filled is a naked short call.
If an algo's entry is refused, the algo closes the legs already in, stops, and shows the reason on its card. You do not need to act, but read the reason before you restart it.
If an algo's exit is refused, it tries again, up to 8 times, with a growing gap between tries, and the card shows what is still owed. Watch it; if the cause is something you can fix, such as a broker sign-in, fix it.
If you placed the legs by hand:
- Check what filled on the Positions screen, grouped by strategy.
- Decide quickly: exit the filled leg, or place the missing leg once the cause is fixed.
- Fix the cause before the next attempt, usually margin or the order type.
When you place a spread or any hedged position, place the bought legs first. The sold legs then get the lower hedged margin and are less likely to be refused. Baskets and algos do this on their own: in a hedged basket, bought legs must fill before sold legs go, so a refused hedge never leaves a naked short option.
Baskets, GTTs and icebergs
- Baskets. Your confirmation is tied to the exact version of the basket you reviewed. If the basket was edited since, it is refused as changed; review it and confirm again.
- GTT changes. A change whose new trigger the price has already reached is refused, because it would fire at once. Choose a trigger the price has not reached.
- Icebergs. An iceberg sends its legs one at a time. A refused, cancelled or part-filled leg, a kill switch or a closed market stops the rest, and the Orders list shows why. Nothing is retried.
Rules that cause refusals on expiry day
- Extra margin. Short index options need an extra 2% margin on expiry day.
- No calendar spread benefit. The margin offset between expiries falls away on expiry day.
- Stock options. Many brokers block new positions in stock options close to expiry, because in-the-money contracts settle by delivery.
Check Funds before the open on expiry day, and place hedge legs before sold legs.
Market orders through APIs
Some brokers require market orders placed through their API to carry a price protection limit, or do not accept them in certain contracts. If market orders are refused, use a limit order priced near the best bid or ask.
Contact support
Write to [email protected] or call +91 97111 30044 with your broker, the instrument, the time, and a screenshot of the order's details sheet. Never send passwords, login codes or broker keys.
Frequently asked questions
Why was my order refused when I have money in the account?
Margin depends on the position, and money already blocked for other positions is not free. Expiry-day margin can also raise the requirement. Check Funds for the free margin.
Does a refused order cost anything?
No. A refused order never reached the market, so no brokerage or charges apply. It costs no tokens either.
Can the kill switch stop me closing a position?
No. The kill switch, the daily loss limit and the maximum orders a day never block a square-off. Only new orders are refused.