Line tests and connectivity

Open line testing

Go to Settings → Customer & support → Line testing. Test and production service checks start automatically, along with spot and futures data checks in the current environment. Each result and retest is independent. Duplicate checks are disabled. Leaving cancels this visit; reopening starts new checks. No active environment or ledger changes.

Read response times

• Green: below 300 ms.
• Yellow: 300–1000 ms.
• Red: above 1000 ms.
• Gray: idle, checking or failed, with “— ms”.

Service tests measure the public request response. Market tests compare connection responses for each available route and select the fastest for the current environment. They do not subscribe to or wait for a quote. The displayed ms is the fastest successful connection response, excluding configuration and total scan time. Each route has a 5-second limit; the overall check is limited to 30 seconds. Failure or leaving cancels selection. The color rules appear once below all results. This measures connection quality, not trade execution or quote readiness.

If a check fails

Check the device network and retest. The test service must be available for that check to succeed. An unsuccessful check does not prevent reading local trades. Successful checks do not prove account login, uploads or cloud synchronization. Addresses and request paths are not displayed.

Market display and cache

Settings → General → Market display controls online prices and the home market card. Settings → Data & privacy → Clear cache lists Market cache. Confirm in the bottom sheet to clear spot/futures quotes and candles in the current environment. Trades, reviews, screenshots, follows and preferences remain. New subscriptions may create new cache. Clearing cache is separate from deleting ledger data.

Check a single line

Each card places the Check action with its icon at the right of the Response time row. Milliseconds and status appear below. While checking, the button is disabled and its label stays Check. You can still use Check all for all four entries; the color rules appear once at the bottom.

Test environment connection failures

The test environment depends on the local API on the development computer and USB port forwarding. If the server is stopped or forwarding is lost after USB reconnection, test and both market checks can fail together. Restore the service and forwarding, then check again. Production is tested separately; test traffic is never silently redirected to production.