WEBVTT 00:00:01.300 --> 00:00:04.995 An entry is the beginning of a position's story, not the end 00:00:04.995 --> 00:00:08.691 of your responsibility. Once a holding exists, its value can change, its 00:00:08.691 --> 00:00:12.386 exit conditions may be monitored, and requests can succeed or fail. Automation 00:00:12.386 --> 00:00:16.082 can help carry out defined work around that position. It does not 00:00:16.082 --> 00:00:19.777 promise that the position will close at an exact price, at a 00:00:19.777 --> 00:00:21.625 convenient moment, or with a profit. 00:00:22.125 --> 00:00:25.997 Open Portfolio and read the identity of a position before judging it. 00:00:25.997 --> 00:00:29.870 The coin is only part of that identity. Inspect its owner or 00:00:29.870 --> 00:00:33.742 strategy, account or connection, mode, and any position identifier shown in the 00:00:33.742 --> 00:00:37.614 detail or action dialog. Two holdings in the same coin can have 00:00:37.614 --> 00:00:41.487 different owners and histories. A result for one should not silently become 00:00:41.487 --> 00:00:43.100 your explanation for the other. 00:00:43.600 --> 00:00:47.447 Position ownership matters when you consider intervention. A holding associated with a 00:00:47.447 --> 00:00:51.294 strategy is not automatically the same as an app-owned or manual holding. 00:00:51.294 --> 00:00:55.141 The app uses these distinctions in its views and actions. Read the 00:00:55.141 --> 00:00:58.988 current labels and any confirmation before changing a position. Do not assume 00:00:58.988 --> 00:01:02.835 that one Sell action will affect every holding with that symbol, or 00:01:02.835 --> 00:01:05.400 that changing ownership preserves the same monitoring behavior. 00:01:05.900 --> 00:01:09.753 The exit-alert view can help you inspect what is being monitored. Read 00:01:09.753 --> 00:01:13.606 the position, the nearest condition reported, and the information available about distance 00:01:13.606 --> 00:01:17.459 or timing. An alert is information about a condition. It is not 00:01:17.459 --> 00:01:21.313 a receipt for a completed sale. After an expected exit, use the 00:01:21.313 --> 00:01:25.166 position and transaction records to check whether an action occurred and what 00:01:25.166 --> 00:01:26.450 amount was actually executed. 00:01:26.950 --> 00:01:30.782 A displayed gain also needs context. Unrealized profit and loss describes a 00:01:30.782 --> 00:01:34.614 holding that is still open, using the valuation available in that view. 00:01:34.614 --> 00:01:38.445 It can change before a sale. A recorded sale has its own 00:01:38.445 --> 00:01:42.277 execution price and fees. Do not treat an open green number as 00:01:42.277 --> 00:01:46.109 cash already secured, and do not expect a later net result to 00:01:46.109 --> 00:01:48.025 equal an earlier screen estimate exactly. 00:01:48.525 --> 00:01:52.416 Stopping deserves the same careful reading. Disabling a strategy, pausing trading, closing 00:01:52.416 --> 00:01:56.307 a position, removing access, and canceling a subscription are different actions. Do 00:01:56.307 --> 00:02:00.198 not assume that a pause closes holdings or that every form of 00:02:00.198 --> 00:02:04.089 stopping leaves exit monitoring active. Some trading controls can block automated exits 00:02:04.089 --> 00:02:07.980 as well as entries. Their scope and the current position state must 00:02:07.980 --> 00:02:10.250 be checked before you rely on them. 00:02:10.750 --> 00:02:14.683 This becomes especially important during an interruption. If you intend to stop 00:02:14.683 --> 00:02:18.616 activity, identify the relevant account and mode, read the control's effect, and 00:02:18.616 --> 00:02:22.548 inspect the returned state. Then check open positions and outstanding results separately. 00:02:22.548 --> 00:02:26.481 If an order had already been sent, a later pause is not 00:02:26.481 --> 00:02:30.414 evidence that the exchange canceled it. Confirm the outcome through the available 00:02:30.414 --> 00:02:31.725 order and account records. 00:02:32.225 --> 00:02:36.019 For your checkpoint, choose one example position and explain who owns it, 00:02:36.019 --> 00:02:39.812 where it belongs, and how you would verify an exit. Finish with 00:02:39.812 --> 00:02:43.606 this distinction: I can see an exit condition, but I still need 00:02:43.606 --> 00:02:47.399 evidence of execution. That habit prevents a common misunderstanding. Monitoring a position 00:02:47.399 --> 00:02:51.193 and finishing a position are related jobs, but they are not the 00:02:51.193 --> 00:02:51.825 same event.