WEBVTT 00:00:01.300 --> 00:00:04.680 A quiet strategy is not automatically a broken strategy. It may be 00:00:04.680 --> 00:00:08.060 waiting for a condition that has not occurred. It may be enabled 00:00:08.060 --> 00:00:11.440 but unable to act because a limit or permission is not satisfied. 00:00:11.440 --> 00:00:14.820 It may also be affected by missing information or a connection problem. 00:00:14.820 --> 00:00:18.200 These situations can all look like no new trade. Your job is 00:00:18.200 --> 00:00:21.580 to separate them using evidence rather than the length of time you 00:00:21.580 --> 00:00:22.425 have been waiting. 00:00:22.925 --> 00:00:26.609 Start with identity and context again. Are you viewing the intended strategy 00:00:26.609 --> 00:00:30.293 in the intended mode and account? Then check whether it is enabled 00:00:30.293 --> 00:00:33.976 and whether the relevant trading state allows activity. A strategy you can 00:00:33.976 --> 00:00:37.660 browse in the marketplace is not necessarily one you have activated. A 00:00:37.660 --> 00:00:41.344 status from the Paper context should not be used to diagnose a 00:00:41.344 --> 00:00:43.800 different Live context without checking that context directly. 00:00:44.300 --> 00:00:47.710 Next, inspect the information the app provides about conditions and candidates. A 00:00:47.710 --> 00:00:51.120 candidate view can help explain what is being considered, but it is 00:00:51.120 --> 00:00:54.530 not a promise that an entry is next. No suitable candidate can 00:00:54.530 --> 00:00:57.939 be a valid result. A market can also move away from a 00:00:57.939 --> 00:01:01.349 condition. You do not need to discover a private strategy formula to 00:01:01.349 --> 00:01:04.475 recognize that the visible evidence does not establish an imminent trade. 00:01:04.975 --> 00:01:08.898 Then check capacity and access. Is the allocation appropriate for the action 00:01:08.898 --> 00:01:12.820 being considered? Are funds already committed? Does the strategy still have the 00:01:12.820 --> 00:01:16.743 access it requires? Is the relevant connection able to submit supported orders? 00:01:16.743 --> 00:01:20.666 Read any specific message before changing settings. A blocked action provides a 00:01:20.666 --> 00:01:24.589 narrower question to investigate. Randomly changing several controls makes it harder to 00:01:24.589 --> 00:01:26.550 know what caused the original problem. 00:01:27.050 --> 00:01:30.646 Missing information requires a different response from normal waiting. A failed load, 00:01:30.646 --> 00:01:34.242 unavailable quote, or connection error means you may not have enough current 00:01:34.242 --> 00:01:37.838 evidence to judge what is happening. Recheck the status and the latest 00:01:37.838 --> 00:01:41.434 available results. Do not treat an old position table as proof that 00:01:41.434 --> 00:01:45.030 no recent action occurred. When the app and exchange information appear inconsistent, 00:01:45.030 --> 00:01:48.626 reconcile the relevant account and time before assuming either view tells the 00:01:48.626 --> 00:01:49.225 whole story. 00:01:49.725 --> 00:01:53.782 A pause or protective interruption also deserves attention. Read the reason if 00:01:53.782 --> 00:01:57.839 one is shown. Do not press resume or reset merely to remove 00:01:57.839 --> 00:02:01.896 an uncomfortable status label. First understand what was stopped, which context is 00:02:01.896 --> 00:02:05.954 affected, and whether existing positions or submitted requests need attention. Removing a 00:02:05.954 --> 00:02:10.011 restriction does not explain its cause or establish that the underlying problem 00:02:10.011 --> 00:02:11.025 has been resolved. 00:02:11.525 --> 00:02:15.182 Imagine that an enabled strategy has made no new trade today. If 00:02:15.182 --> 00:02:18.838 its context is correct, data is available, and no blocking message appears, 00:02:18.838 --> 00:02:22.495 it may simply be waiting. If the connection reports an error, that 00:02:22.495 --> 00:02:26.151 is a different starting point. If the displayed state cannot be confirmed, 00:02:26.151 --> 00:02:29.808 say so. Three different explanations call for three different investigations; none is 00:02:29.808 --> 00:02:32.550 solved by assuming that more activity must be better. 00:02:33.050 --> 00:02:36.805 Your checkpoint is to sort an example into waiting, blocked, or uncertain. 00:02:36.805 --> 00:02:40.559 Say what evidence supports your choice and what you would inspect next. 00:02:40.559 --> 00:02:44.314 If you need help, record the time, mode, strategy, and exact message 00:02:44.314 --> 00:02:48.069 without including credentials. A specific report gives someone a place to start. 00:02:48.069 --> 00:02:51.823 The robot did nothing is an observation; the surrounding facts turn it 00:02:51.823 --> 00:02:53.075 into a useful question.