I propose that CQG should add the option of Stop Loss at Market (including its use within OCO orders and regular order placement) on iOS, Android, and PC platforms. Stop Loss at Market means not allowing stop loss orders created by OCO and manually placed orders to be rejected, resulting in loss of the stop loss order. This poses a significant risk to investors, especially during volatile market conditions. In such scenarios, there could be gaps or rapid price movements that exceed the stop loss price when the order is executed. In such cases, Stop Loss at Market would execute the stop loss at the current market price instead of rejecting it. For instance, if I set a stop loss of 3 ticks with a price of $50 using an OCO order, and the price rapidly moves against my prediction causing a loss, but exceeds my stop loss price immediately upon execution or creates a significant gap, in this case, the system needs to cut the loss at the current market price. Assuming it results in a loss of $200, it's still preferable to having the stop loss rejected, which could potentially lead to a much larger loss of more than $200 if I fail to manually exit the position in time. Furthermore, at that crucial moment, if there is a slowdown or an error in the internet connection, investors could suffer catastrophic losses due to the absence of preset stop loss orders. Notification of rejected stop loss orders, after the fact, sometimes does not address the issue. Many investors, including myself, have encountered this situation, and fortunately, there have been no instances of account depletion due to timely manual intervention.