Can My AI Trading Agent Place the Same Order Twice?

Picture the smallest possible failure. We tell an AI trading agent to buy 40 shares. It sends the order, and then the confirmation never comes back. The screen just sits there. Did the order reach the market, or not? On July 3 this stopped being a thought experiment for more of us, because Robinhood extended its agentic trading to crypto, where an agent can place orders 24 hours a day, seven days a week, with no overnight pause to sort out what actually happened. The equity version had launched five weeks earlier, on May 27. The plumbing question underneath all of it is one most of us never think about: what does an agent do when it is not sure its own order went through?

Why a timed-out order is not a failed order

When any piece of software places an order, it sends a request and waits for an acknowledgement. A timeout means the acknowledgement did not arrive in time. It does not mean the order failed. The order may have reached the broker and filled, and only the reply got lost on the way back. So an agent that treats “no answer” as “it did not work” and resends has just manufactured a real risk of two orders from one intention.

What decides whether that second attempt becomes a second position is not the agent’s intention. It is whether the order carried a unique tag the broker recognizes as a repeat. In a real retail trading interface like Alpaca’s, that tag is called the client order id. If the software attaches the same tag to the retry, the broker sees the duplicate and rejects the second copy with a rejection it numbers 422, reading “client_order_id must be unique.” If the software attaches a fresh tag, or none at all, the broker has no way to know the two requests were meant to be one, and both can fill.

This is the property engineers call idempotency: an operation you can safely repeat because repeating it changes nothing. Reading an account balance is naturally idempotent. Placing an order is not, unless someone deliberately makes it so, usually by attaching that unique tag and having the broker remember it for a window of time, commonly around 24 hours.

What Robinhood’s round-the-clock crypto agents change about the retry problem

The bring-your-own-agent wave is now large enough that this stops being hypothetical. In the weeks after Robinhood opened agent access, more than 50,000 agent accounts were created, and eToro reported roughly 500,000 agent trades. The brokers are candid about what they are handing over. Robinhood’s own agentic trading page states, in plain terms, that “Robinhood does not control, supervise, monitor, recommend, or audit these AI agents,” and that “AI agents can make errors, misinterpret instructions, act on incomplete or outdated information, and may behave in unexpected ways.” On July 2, the company’s chief executive spent the day arguing that agents will eventually match the capability of human traders.

Here is the part worth sitting with. These platforms add a human-approval step: the agent proposes a trade, and we approve it before it goes to market. That gate approves the first submission. It does not approve the silent retry that happens underneath, machine to machine, if the first attempt times out. And the retry matters most on a fast day. The last session before the holiday, on July 2, closed with the Dow at a record near 52,900 and the Nasdaq Composite down 0.8%, after a jobs report that missed badly. A duplicated order fired into a moving tape fills the second, unwanted copy at whatever the price has become, not the price we approved.

The approval button we can see governs whether the trade is a good idea. It does not govern whether one good idea reaches the market once or twice.

The one question to ask before an agent touches a funded account

We cannot see the broker’s deduplication logic from the outside, and we should not pretend to. What we can do is treat retry-safety as a named feature rather than an assumption. Ask the platform, or its documentation, a concrete question: if the agent’s order request times out, does the system reconcile against existing orders before it resubmits, and does it attach a unique tag the broker rejects on repeat? A precise answer names the mechanism. A vague answer, “our system is reliable,” is the tell. For anyone wiring an outside ai agent for stock trading into a funded account, the same discipline holds. Keep the resting balance small enough that a doubled order is an annoyance and not an event, until the retry behavior is something we have confirmed rather than hoped for.

The Knight Capital episode in 2012 is the reminder that automated order errors do not stay small. A runaway system sent millions of unintended orders and cost the firm about 440 million dollars in roughly 45 minutes. That was a deployment flaw, not a retry, but the lesson travels. The failure that costs the most is rarely the trade we argued about and approved. It is the one the machine repeated while we were still looking at the confirmation that never came.