When trading is paused

The ticket pauses when account access, market identity, prices or the engine connection cannot be verified. New commands are rejected during engine recovery. A halted or stale book cannot provide an executable fill.

Check your connection and the status page, then return to the workspace. An engine connection does not guarantee every account or game is tradable. Do not bypass a pause through another profile or repeated orders.

A missing display does not mean a position disappeared. Stale positions keep prior marks. Fresh positions, cash changes and recorded settlements can still affect equity; a frozen number is not a protected balance.

After recovery, risk checks resume when the required mark pass has at least one fresh held position, or no positions remain. They do not wait indefinitely for every market to refresh. The first available prices can reveal a breach.

Previously committed results stay in history. Commands waiting in the simulation-delay window at restart are rejected with an engine-restart reason. No fills are invented for downtime.

If the outcome is not confirmed, use Check order status and keep the original ticket until a final result is known.