A buy, then a sell, then another buy
Imagine checking your phone while brushing your teeth and finding a stack of trade emails. Your bot kept buying and selling while you slept. The account balance is the consequence; the repeated orders are what you need to stop and explain.
Start with your approval between the agent and the broker. Keep the event trail that explains each decision. If you later enable automatic approval, give it a daily allowance so the next action returns to your review when that allowance is spent.
1. Make the order wait for you
An agent proposes a buy. You inspect the symbol, quantity, order type and reason. Until you approve it, that proposal stays on the review side of the gate. Your approval lets the same order proceed to the broker.
In NexusTrade, strategy evaluation and automatic order approval are separate controls. Automated Trading evaluates the rules. Autonomous Trading governs eligible automatic approvals for live trading. The default portfolio policy has automatic approval disabled; only you can enable it through the app after the required account approval and consent.
Keep approval with you
Open the intended portfolio and inspect its Trading Policy. For your first bot, keep automatic order approval disabled.
A new live order proposal requires your review.
Read the waiting proposal
Check its symbol, quantity, side and order type against the strategy that produced it.
The proposal is pending your approval, rather than already submitted to the broker.
Follow the approved order
When you choose to approve an order, follow that exact order through submission and status updates.
Submission and fill remain separate states. Verify the actual broker result.
2. Open the events that caused the loop
A buy followed by a sell tells you that two actions happened. Open their events to find out why. Read the time, strategy, action and order status, then inspect the condition values and pass/fail result where the event contains audit data.
Suppose a buy rule passes because price 101 is greater than threshold 100. A sell rule then passes because held shares 10 is greater than zero. If both remain true on successive evaluations, the event trail gives you a concrete conflict to investigate. These numbers are a worked example, not a record of an actual account incident.
Compare the buy and sell rules together, including their position guards and evaluation timing. Reproduce the corrected rules in a backtest and observe them in paper trading. Keep the event record from the run you are examining; changing a strategy later does not make every old event a complete snapshot of every prior setting.
Select the buy event
Follow the recorded values into the buy condition.
101 > 100 passes, producing a buy signal and its order.
Select the sell event
Follow the next event into the sell condition.
10 held shares > 0 also passes. Investigate why the rules allow an immediate reversal.
Test the repair
Use a backtest and a separate paper run to inspect the revised rule interactions.
You can explain each action using its recorded event and the rules being tested.
3. Put a circuit breaker on automatic actions
Set the automatic allowance to two trade actions for this example. The first eligible action uses one allowance. The second uses the other. When a third action arrives, the automatic path is closed and the action waits for your approval.
That daily allowance is the circuit breaker shown here. NexusTrade counts trade actions within an Eastern calendar day. Once the allowance is spent, additional actions take the semi-automated route with the reason DAILY_LIMIT_REACHED and wait in PENDING_USER_APPROVAL. You can still choose to approve them manually.
A trade action can contain multiple child orders, such as a rebalance. The allowance therefore limits automatic actions, not necessarily the number of individual broker orders. It also does not cap the dollars in an order or cancel orders already at the broker. Review sizing, open orders and holdings separately.
First eligible action
The example buy passes the policy check.
The counter moves from 0/2 to 1/2.
Second eligible action
The example sell receives the remaining automatic allowance.
The counter moves from 1/2 to 2/2.
Third action
The bot proposes another action after the allowance is spent.
The action waits for your approval. It does not receive a third automatic grant.
Inspect your own setup before enabling anything
Open the portfolio you intend to use and identify the approval mode, current daily allowance and recent events. Ask Aurora to explain those exact records, then compare its answer with what the app shows. Keep live trading and policy changes under your control.
No comments yet.