WEBVTT

00:00:01.300 --> 00:00:05.742
A dashboard is useful when you understand how current its information is.

00:00:05.742 --> 00:00:10.184
The screen being open does not prove that every part has finished

00:00:10.184 --> 00:00:12.775
loading or that every service is responding.

00:00:13.275 --> 00:00:17.661
Start with the update connection indicator. When it says Live connected, it

00:00:17.661 --> 00:00:22.047
reports the connection used for live updates. Here, live describes the flow

00:00:22.047 --> 00:00:26.433
of information. It does not select Live trading mode, verify every exchange

00:00:26.433 --> 00:00:30.819
permission, or prove that an order succeeded. Check those things in their

00:00:30.819 --> 00:00:31.550
own places.

00:00:32.050 --> 00:00:36.068
If the indicator offers Connect live updates, the update connection is not

00:00:36.068 --> 00:00:40.086
currently active. If it asks you to sign in, account access needs

00:00:40.086 --> 00:00:44.104
attention. Read the actual message you see. Different parts of the app

00:00:44.104 --> 00:00:48.121
can depend on different requests, so one healthy indicator does not guarantee

00:00:48.121 --> 00:00:50.800
that a balance or chart has loaded successfully.

00:00:51.300 --> 00:00:55.579
Now separate four situations. Loading means the app is still trying to

00:00:55.579 --> 00:00:59.858
obtain information. An empty result means the current request or view has

00:00:59.858 --> 00:01:04.137
no items to show. Stale information means you may be seeing an

00:01:04.137 --> 00:01:08.416
older result. An error means something prevented the requested information from being

00:01:08.416 --> 00:01:11.625
obtained or displayed normally. These states need different explanations.

00:01:12.125 --> 00:01:16.132
Imagine that Portfolio has no rows. Perhaps there are no positions in

00:01:16.132 --> 00:01:20.139
this mode. Perhaps a filter hides them. Perhaps the request has not

00:01:20.139 --> 00:01:24.145
finished. Read the surrounding labels and messages before deciding. An empty panel

00:01:24.145 --> 00:01:28.152
by itself does not prove that the account has a zero balance.

00:01:28.152 --> 00:01:31.825
A dash beside a value is not the number zero either.

00:01:32.325 --> 00:01:36.475
Look for a displayed update time, reference delay, loading message, or error

00:01:36.475 --> 00:01:40.625
notice when one is available. If there is no visible timestamp, do

00:01:40.625 --> 00:01:44.775
not invent one. Say that freshness has not been confirmed. This is

00:01:44.775 --> 00:01:48.925
especially useful when comparing a chart, a balance, and a transaction record

00:01:48.925 --> 00:01:51.000
that may update at different times.

00:01:51.500 --> 00:01:55.436
When something looks wrong, first confirm your mode and account context. Then

00:01:55.436 --> 00:01:59.371
check the search or filters and read the message. Allow a loading

00:01:59.371 --> 00:02:03.307
request to finish. Use a retry or refresh control if the affected

00:02:03.307 --> 00:02:07.242
view offers one. If the issue continues, note the affected section and

00:02:07.242 --> 00:02:10.850
the message so you can seek help without sharing account secrets.

00:02:11.350 --> 00:02:16.250
One situation deserves extra care: an uncertain order result. Refreshing a view

00:02:16.250 --> 00:02:21.150
is not the same as submitting the order again. Check the relevant

00:02:21.150 --> 00:02:26.050
activity and exchange record before repeating a financial action. Our troubleshooting chapter

00:02:26.050 --> 00:02:28.500
will cover that process in detail.

00:02:29.000 --> 00:02:33.246
For this page's check, explain the difference between an empty account view

00:02:33.246 --> 00:02:37.492
and a failed balance request. Then find the update indicator and explain

00:02:37.492 --> 00:02:41.738
what it tells you, without using it as proof of trading mode

00:02:41.738 --> 00:02:42.800
or trading success.