Treat the signal carefully
Invalid account is a stronger signal than a generic pending sync, but it still needs the surrounding evidence. The same visible phrase can appear after a wrong login, wrong server, disabled account, or rejected password context.
Golden Trading Cup should use fresh runtime or broker evidence before telling a trader that a server, login, or investor password needs attention.
Checks that usually matter
First confirm the MT5 login number, not the broker portal ID. Then confirm the exact server name exactly as shown in MetaTrader 5.
If both are correct, the next useful check is whether the investor password is active for that account and whether the broker has disabled, migrated, archived, or restricted the account.
What not to do
Do not repeatedly retry random nearby servers. That can hide the real issue and produce noisy support evidence.
Do not paste passwords into chat. If a reconnect is needed, use the secure connection flow and keep support focused on the non-secret facts around the failed attempt.
Evidence that makes it actionable
The most actionable invalid-account case is a fresh broker or runtime rejection that names the submitted login and exact server context. That evidence is stronger than a stale cache label or an old generic worker error.
If the latest evidence is only a timeout, LiveUpdate noise, or a pending queue state, Golden Trading Cup should avoid telling the trader that credentials are wrong. The support verdict should match the freshest primary signal.
Next step by cause
If the login is wrong, the trader should reconnect with the MT5 login number. If the exact server is wrong or unsupported, support should classify that exact server before more retries. If the account is disabled, broker-side action is required first.
If the investor password is the likely mismatch, the trader should update it through the secure app flow rather than posting it to support. The public pages should continue to show only safe status context.
Key takeaways
- Invalid account should be confirmed with fresh evidence.
- Login number, exact server, and investor password context must match.
- Retries should be targeted, not random server guessing.