ഉള്ളടക്കം · 3 / 4
Broker connection and import problems
പുതുക്കിയത് 6 ഓഗസ്റ്റ് 2026 · 2 മിനിറ്റ് വായന · 10 ഉള്ളടക്കം
ലളിതമായ അർത്ഥം
Broker connections are read-only and depend on the broker's own authorization flow. Most failures are expired tokens, incomplete authorization or broker-side outages, and re-authorizing is the usual fix.
Where it appears #
Symptoms appear on the Brokers page as configured-but-disconnected status, a failed authorization return, or an import preview with missing fields.
Step-by-step workflow #
1. Check the broker's configured and connected status separately. 2. Re-authorize on the broker's own page, or paste a fresh temporary token where that method applies. 3. Return and confirm connected status. 4. Preview holdings before importing. 5. Review rows with missing exchange or price: they stay unavailable rather than guessed. 6. Import, then verify quantities against your broker statement.
Worked example #
A broker can be configured because its app key exists yet disconnected because today's access token expired overnight. Re-authorizing restores the connection without changing previously imported holdings.
How to interpret the result #
Configured describes operator setup; connected describes your current authorization; imported rows describe evidence the broker actually returned. None of these states alters market data.
Limitations and common mistakes #
Never send broker tokens through feedback, screenshots or logs. An import is a snapshot, not a live sync, and broker payload fields differ, so review is always required.
Market-specific differences #
OAuth flows, token lifetimes and holdings fields differ by broker and country; unsupported brokers simply do not appear in the catalogue.
Educational use only #
This guide is descriptive education, not investment advice, a prediction, a recommendation, or an instruction to buy, sell, rebalance or place an order.