An instruction with several parts
An order ticket brings together a market, a direction, a volume and an execution instruction. Read those fields as one instruction rather than concentrating only on the price. Check whether the screen is creating a new order, editing a pending instruction or closing an existing position. These actions can look similar on a compact mobile interface.
Understand what the order type controls
Market, limit, stop and stop-limit orders express different conditions. In the cTrader documentation, a stop order activates a market order, while a stop-limit instruction activates a limit order. A trigger being reached and an order being filled are different events. Read the current platform help for the exact behavior and available settings.
Review the parameters in context
Check the instrument identifier, volume units, price fields and expiry. Find the platform instructions for amending or cancelling a pending order. An instruction left active can remain relevant after you stop looking at the chart. Do not assume that a saved volume or a previously selected account is the one intended for the next instruction.
Keep the acknowledgement
After an instruction, read the resulting status and account history. Save the order reference, submission time and any error message when asking support about an unexpected result. An interface screenshot can help describe a question, but it does not establish why a particular execution occurred.