1) If there's insufficient margin, it'll display as rejected.
Conditional orders don't initially require a margin when placed. However, when triggered (once the preset price - LTP/ Mark hits the trigger), the system checks for margin availability. If there's not enough balance to execute the order, it'll be rejected.
Note: When manually setting a stop loss via a conditional order, remember to opt for the Close on Trigger function. (only supported on one-way mode)
2) If Close on Trigger is mistakenly selected when placing conditional orders to open a position, it'll show as rejected.
Close on Trigger is strictly for closing positions. If a conditional order with Close on Trigger is triggered without an existing open position, the system will reject the order.
The following reasons pertain specifically to conditional limit orders:
1) If the order price is set to a level better than the best bid/ask price within the order book when triggered, it'll appear as NEW.
Conditional limit orders, upon triggering, act like placing a limit order at that moment. Execution depends on the preset order price relative to the best Bid/Ask price within the order book. These orders remain active but unexecuted until the Last Traded Price (LTP) reaches the order price or until users decide to cancel them.
2) If the post-only function is selected and the conditional limit order is immediately executed upon triggering, it'll show as canceled.
The purpose of the post-only function is to ensure that traders' conditional limit or limit orders enter the order book before execution, qualifying as maker orders and thus paying a maker fee. If the system detects that the order would be immediately executed upon triggering, it automatically cancels the order to prevent traders from inadvertently incurring taker fees.
