Change Your Broker Password Without Losing Your Setup

Brokers expire passwords. Some do it on a schedule, some do it when you log in from a new country, and some do it for reasons they never explain. It is a normal, boring event that happens to everyone eventually.

Until now, handling it in TTMT meant disconnecting the account and adding it back. Which cost you a slot for as long as the cycle took, and dropped the thing you actually cared about: which channels routed to that account, what settings it carried, and the history attached to it.

You can now update the credentials in place. Routing, settings and history stay exactly as they were.

Two entry points. Account details, whenever you want. Or the amber strip we show when we have detected a credentials problem, which takes you straight there.

We now say when it is the password

Related, and the more useful half of this. A stale broker password used to surface as a generic disconnection, with a suggested fix that could never work. You would sit there reconnecting an account whose password was wrong, watching it fail, with nothing telling you why.

It now reads as "credentials invalid" and points at the password change.

Limit orders can wait ten days

Swing channels needed this. A limit order can now stay live for up to ten days if you want it to, rather than being cancelled by a timeout designed for intraday setups.

That pairs with a change in the other direction, which I have written up separately: unfilled limits now expire after thirty minutes by default.

Per-asset overrides say which setting wins

When a per-asset override and a channel default disagree, the rules are now stated rather than implied. Sizing and take-profit pips go to the override. Stop-loss pips lose to the channel default.

You can argue with that precedence and some people will. The point is that it is written down and consistent, instead of being something you discover by comparing two trades.

The rest of the release

Failure reasons now come from the trade record in plain language. For traders with a single account the real reason was being overwritten by an internal reference about a tenth of a second later, so every single-account failure was opaque. Notifications had the same problem: 84% of broker-error alerts in one month were unreadable tokens.

AI trade explanations are grounded on verified facts about the trade rather than generated loosely from context.

The dashboard tells you when your trading service is asleep instead of rendering as though everything were live. Paying again wakes it, redeploys your accounts and revives paused channels without a support ticket.

A "close 50%" instruction could close the whole trade, because rounding to the broker's minimum lot step over-closed. That hit 76 trades across 16 traders. Fixed.

A failed read of your open positions was being treated as "you have no positions" rather than "we do not know", which could finalise a trade as closed while the broker still held it live. It now distinguishes the two, which sounds obvious and is the single most common class of bug in software that talks to brokers.

A cleanup sweep marked 24 limit orders cancelled and the trade Not Filled, but the broker had refused those cancels. All 24 stayed live, filled five hours later and ran to the stop while the dashboard showed nothing. The sweep now verifies the cancel landed before it writes anything down.

With Best-Price Entry on, take-profit targets were still being measured from the pre-Best-Price edge of the zone, so a 100-pip target could end up 170 pips away.

Once you pressed Reconnect, a false red "connection down" banner could never clear again.

With two alerts on the same symbol and direction both awaiting details, a follow-up could attach to the wrong one.

Account conversions to self-hosted execution had never once completed. Every attempt died about a minute in. They complete now.

Start a free 7-day trial at telegramtometatrader.com, or read how TTMT watches a trade after it's placed.