WEBVTT 00:00:01.300 --> 00:00:05.414 Selling one position and requesting sales across a portfolio have very different 00:00:05.414 --> 00:00:09.527 scope. This page explains the wider controls using a demonstration. You do 00:00:09.527 --> 00:00:13.641 not need to sell your whole Paper portfolio to complete the lesson. 00:00:13.641 --> 00:00:17.754 The skill is to understand what would be requested, which positions are 00:00:17.754 --> 00:00:21.525 included, and what evidence would show that the separate actions succeeded. 00:00:22.025 --> 00:00:26.672 In the desktop summary, Potential Cash Realize opens the portfolio-wide sale review 00:00:26.672 --> 00:00:31.319 when available. The amount is an estimate, not cash already in your 00:00:31.319 --> 00:00:35.967 account. Opening the review does not submit the sales. Inspect the positions 00:00:35.967 --> 00:00:40.614 listed below the estimate, including each owner or strategy, account or connection, 00:00:40.614 --> 00:00:42.550 position identity, and available quantity. 00:00:43.050 --> 00:00:47.034 Each row creates its own sell request. Holdings with the same symbol 00:00:47.034 --> 00:00:51.017 but different owners are not combined into one anonymous balance. If a 00:00:51.017 --> 00:00:55.001 position cannot be identified or the list cannot be loaded correctly, the 00:00:55.001 --> 00:00:58.984 app can block submission. That is a reason to refresh and reconcile 00:00:58.984 --> 00:01:02.968 the information, not a reason to guess which holding a total must 00:01:02.968 --> 00:01:03.300 represent. 00:01:03.800 --> 00:01:08.010 The two choices are labeled Sell all and continue trading, and Sell 00:01:08.010 --> 00:01:12.220 all and pause trading. The first requests the reviewed sales without requesting 00:01:12.220 --> 00:01:16.431 a trading pause. It does not turn an already paused system back 00:01:16.431 --> 00:01:20.641 on simply because the word continue appears. If automation is running and 00:01:20.641 --> 00:01:24.500 remains allowed to trade, closing positions does not prevent later activity. 00:01:25.000 --> 00:01:29.258 The second choice requests the reviewed sales and also requests a trading 00:01:29.258 --> 00:01:33.516 pause. These are separate operations. The current flow handles the position requests 00:01:33.516 --> 00:01:37.774 and then asks for the pause. Do not picture one instant switch 00:01:37.774 --> 00:01:42.032 that guarantees every holding disappears and all activity stops together. You must 00:01:42.032 --> 00:01:45.225 inspect both the position outcomes and the pause confirmation. 00:01:45.725 --> 00:01:49.748 One position might fill while another is not confirmed. A request might 00:01:49.748 --> 00:01:53.771 be accepted without a confirmed fill, or accounting may still need to 00:01:53.771 --> 00:01:57.794 catch up. A pause can fail independently of the sales. Read each 00:01:57.794 --> 00:02:01.817 row's result and any overall message. Trading pause confirmed is useful evidence 00:02:01.817 --> 00:02:05.840 about the pause; it does not certify that every sell request filled 00:02:05.840 --> 00:02:06.175 completely. 00:02:06.675 --> 00:02:10.895 If a retry is offered within the same portfolio review, it follows 00:02:10.895 --> 00:02:15.114 the existing plan of requests rather than treating the portfolio as a 00:02:15.114 --> 00:02:19.334 fresh, unrelated batch. Still, inspect unresolved rows and records before taking another 00:02:19.334 --> 00:02:23.554 action. Closing and reopening a review is not a substitute for knowing 00:02:23.554 --> 00:02:27.773 what the earlier requests did. Keep the request details needed to follow 00:02:27.773 --> 00:02:28.125 up. 00:02:28.625 --> 00:02:32.625 Your summary should answer two questions separately: which quantities were actually sold, 00:02:32.625 --> 00:02:36.625 and is trading confirmed paused or still able to continue? Then compare 00:02:36.625 --> 00:02:40.625 the refreshed positions and cash with the recorded activity. All in a 00:02:40.625 --> 00:02:44.625 button label describes the requested scope, not a guaranteed outcome. That distinction 00:02:44.625 --> 00:02:48.625 lets you supervise a broad action without assuming that one response tells 00:02:48.625 --> 00:02:49.625 the whole story.