Troubleshooting Bridge

Work through these in order. Most problems are one of the first three.

The hub URL does not match. The web app shows the communication hub URL in the Desktop Bridge card and states that Bridge must use the same one. If they differ, the two applications are on different channels and nothing else will work. Fix it in Bridge Settings, Communication.

The communication ID is wrong. Copy it again with Copy ID and paste it into Bridge. A partial paste produces a connection that looks fine and reaches nobody.

One side is not connected. Both need a live connection to pair. Check the chips in both applications, and use Connect in Bridge and the refresh control in the web app.

The echo test fails. Run it from either side. If the echo does not come back, the pairing code will not work either, so fix the channel first. The web app reports no pong from Bridge and asks whether both use the same hub and communication ID.

Pairing times out. The code lasts two minutes. Press Retry in the web app for a fresh one rather than reusing the expired digits.

A broker fetch fails. Test the broker connection in Bridge settings. For DAS and TWS, confirm the platform is running and its API is enabled. For Tradervue and Flex Query, confirm the credentials and the query ID are current.

A send is refused. Check the account alias in Bridge against the one selected on the Import screen. Also check that pairing is active, since an unpaired Bridge cannot upload and will say so.

Symbol sync reads nothing. Confirm the screen capture permission is granted to TraderReflex Bridge in your operating system privacy settings, then re-select the region and use Preview to see what it actually captures.

If you need to start clean, Clear All Credentials in the Security tab resets Bridge completely, and you can pair again from scratch.