Troubleshooting
Connection Problems
Common reasons why UID, API, portfolio or runtime snapshot is not ready.
English localization is preserved as a draft. It uses the same claim IDs and status model as the Russian source, but remains noindex until editorial review.
Most connection problems belong to one step: email, Telegram, UID, API validation, portfolio sync or stale runtime state. The cabinet should show the nearest next step instead of hiding the error.
If an issue involves API permissions or runtime recovery, the safe public path is to check the cabinet status and contact support. Unverified security or trading-behavior guarantees are not published in this release.
Common Causes
- UID has a typo or is not approved yet.
- API validation returned invalid/error.
- Portfolio artifact is missing or stale.
- Runtime request became stale: open request is older than 180 seconds.
What To Do
- Check the current step status in the cabinet.
- Fix UID/API if the cabinet shows an error.
- Refresh portfolio snapshot if refresh is available.
- Contact support if failed or stale status repeats.