"No connection" / account disconnected

You can meet this in two places: on Trading Accounts, where the account card has a red status dot and usually a message under its name, and in Trading Hub → Execution Log, where an order can fail with retcode=10031 desc=No connection (open the signal's row to read the error).

First: is it the nightly window?

Most brokers run a short maintenance window daily, usually around the daily rollover. MetaTrader reconnects to the broker on its own when it is back. If the disconnect happens at the same time every day, that is what it is — check the Execution Log for anything missed during it.

If it is not

1. Reconnect first. Press the connection icon (tooltip Connect) on the account card, or open the account and press Connect — or Retry connection in the red "Connection failed" box.
2. Log in with the platform directly. If MetaTrader itself cannot connect with the same three values, the problem is at the broker: account disabled, password reset required, or a server change.
3. Re-check the server name. Character for character — see Finding your exact MT5 server name. If the account never connected, a live login on a demo server produces the same failure as a wrong password.
4. Check what else uses the login. Another system trading the same account can interfere with PipSync's orders and positions. Give PipSync its own account if you can.
5. Password changed at the broker? There is no form to change a saved password. Delete the account (trash icon on its card — this also removes its channel links, trade history stays), add it again with the new password, then link it to your channel again (Channels → your channel → Per-account settings). If a channel is left with no enabled linked account, PipSync switches its auto-trade off when the next signal arrives and sends the notification "Auto-trade disabled — reconnect an account".

While disconnected

• Orders cannot be sent. A No connection refusal means the order never reached the broker, so PipSync retries it twice (after about 12 and 25 seconds). If it still fails, that trade fails.
• There is no "blocked" state and no replay. PipSync does not fire a missed signal later when the connection returns, because its entry price would be stale. If every linked account failed, the signal shows as Rejected in the Execution Log; a signal that was never finalised is marked rejected about 30 minutes later.
• A stop loss and take profit that were sent with an order are held by the broker. Anything PipSync would do later — moving the stop, partial closes, closing on a signal update — cannot be sent while the account is disconnected.