Your Trading Platform Froze. Did the Order Go Through?

Consider a hypothetical incident: you have no open position or working order, press Submit to open a trade, and the application stops responding before showing a confirmation or rejection.

The missing confirmation changes your next decision

You know what you intended to submit. You do not yet know whether the instruction reached the account, whether it was accepted, or whether any quantity filled. The frozen display cannot settle those questions.

That uncertainty makes another press of Submit consequential. If both instructions are accepted and filled, you could end up with more exposure than planned.

On an evaluation or funded account, that exposure also matters for the account's rules. Where a loss limit includes open-position profit and loss, a filled order continues to affect the monitored value while your screen is frozen. In futures, separately accepted entries can together exceed the permitted contract count.

The same gap applies to protection. If you intended to attach a stop, intention alone does not confirm that the order is present and active. Where an order or an automated function runs matters when access is interrupted. PFW's platform workflow guide explains why the application, hosted service and account server need separate checks.

Use the recovery procedure and support route documented for that account and connection. Evidence collection should not delay an available, supported risk-control action.

Preserve the gap in the record

While following that procedure, retain the account ID, application and version, connection, selected instrument, attempted instruction, timestamp and timezone, and any visible message or order reference. Save available screenshots and logs. If no order ID appeared, record that none appeared, and note which clock each time comes from.

In this scenario, the useful description is narrow: you pressed Submit, the display stopped responding, and you saw neither confirmation nor rejection. Writing "the order was rejected" would quietly turn missing information into a conclusion. A screenshot preserves what you saw, but leaves the account's activity during the gap to be established from its records.

Ask about this order

Through the account's established official contact route, identify the affected account and the attempted instruction. Ask whether it was received and what order or execution records correspond to it. Include the available reference and timing rather than relying on a general report that the platform froze.

A service-restored notice can be useful, but it leaves your particular order unanswered. If a response does not address that order, keep the question open, with the ticket and full exchange. PFW's guide to conflicting rules treats a reply that does not address the applicable account as unresolved. The same test applies here: does the reply answer the order question you asked?

Any request for a reset, adjustment or reimbursement is a separate question under the applicable incident policy. Recording a freeze does not establish entitlement to one.

A moving chart is only the start of recovery

Now suppose the application responds again. Before treating the interruption as over, match the attempted instruction to the account records. Establish what remains working, what quantity filled, what position is open and what protective orders are actually present, including any left without the position they were meant to protect. If nothing is open, check the history too: an empty position panel alone does not explain what happened during the gap.

Reconcile the recorded fills and charges with the account statement, including any recorded rule event. The execution record in PFW's execution guide gives the detailed fields for that check. If the records still do not connect the instruction to an outcome, report the exact missing link through the same official route.

Before the next session, write down what the incident showed you lacked: the account's supported recovery procedure and support route, where its orders and any automation run, and what persists after disconnection. PFW's platform guide includes these among the checks to make before an incident. If the original instruction is still unaccounted for, the freeze has ended but the order question remains open.