A connection-lost message means the application reported a lost connection; it does not by itself establish that positions were closed or orders canceled. Record the error and timestamp, identify the affected service, and confirm account state through an available supported route or your provider. Use the recovery procedure for the actual platform.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
First response
- Record the full message and timestamp with timezone before clearing it.
- Identify which application and service failed. A chart, price connection and trading connection are not interchangeable observations.
- If orders or positions may exist, establish their current state through a connected account view or the provider's supported procedure.
- Identify whether local software manages any bracket, OCO or trailing actions before restarting it.
- Review the recorded outcome of an earlier submission before sending it again.
The last step matters when the connection drops between submitting a request and seeing its outcome. Repeating the request is not a safe way to find out what happened.
Interpret the visible state
| What you see | What it tells you | What to check next |
|---|---|---|
| Disconnected message | This application reported a connection failure | Log details and the named service |
| Frozen chart | The display has stopped changing | Contract, market hours, data timestamp and data service |
| Empty positions panel | This panel shows no rows | Connection/account scope and refreshed account state |
| Green service indicators | Services reported connected at that time | Account permissions, orders and quote freshness separately |
No disconnect was created to obtain an error screenshot for this article. The observed reference is labeled so it cannot be mistaken for a reproduction of the failure.
Find the correct recovery instructions
For repeated losses, use the connection-drop investigation. It separates session conflicts, plugin dependencies, local/network issues and connector-specific behavior.
The Sierra Chart Rithmic guide documents its own commands and a particular recurring-disconnect pattern. Quantower's issues guide covers its direct/plugin causes. Use the matching branch; do not copy another application's command or diagnosis.
After recovery, verify account, positions, working orders and automation state using the reconnect checklist. Restored prices alone do not complete that check.
Escalate with evidence
Share the exact message, application/version, time, System/Gateway, affected service and any other connected apps. Include relevant redacted logs and the checks already completed. Use the provider's official urgent-trading channel if account state requires immediate confirmation. Do not send passwords.
Common questions
Does connection lost mean my trade was closed?
No such conclusion follows from the message. Confirm the current account record.
Can my stop still be working?
Its state depends on the actual order and route. Check the working-order record and where its management runs; do not infer either survival or cancellation from the disconnect alone.
Should I immediately send a replacement order?
First verify whether the earlier request was accepted, rejected, filled or canceled. The outcome may be uncertain during a disconnect.
Do green indicators prove everything recovered?
They are service-status observations. Verify the intended account, data and order/automation state separately.