TradeStation Not Taking Orders: Causes and Fixes
TradeStation refusing your orders? Read the rejection message first. Here are eight common causes and how to fix each one fast.
Marketing
When TradeStation is not taking orders, the rejection message attached to the failed trade is the fastest diagnostic tool you have. That message usually names the exact rule or condition that blocked the order, and each cause has a different resolution path. Reading it first saves time that would otherwise be spent changing strategy settings that are not the problem.
The causes fall into a few families: price increment mismatches, asset class restrictions, account provisioning delays, extended hours rules, buying power limits, and filters that stop a signal before it ever reaches TradeStation. Each section below addresses one family, explains why it happens, and describes the shortest path to a fix.
Read the Rejection Message First
Where to find rejection text
TradeStation surfaces rejection reasons at the order level, not as a generic failure notice. The rejection text usually names the specific rule or condition that blocked the order, which points directly to the fix. Changing strategy settings before reading that message wastes time and can introduce new problems on top of the original one.
In TradersPost, the strategy signals log shows every inbound webhook request, the time it was received, and any rejection reason returned by the broker. Clicking into an individual trade record shows the full rejection message, giving you a single place to distinguish a platform-level block from a TradeStation-level rejection.
Same symptom, different causes
An order that silently fails to execute can be stopped by TradeStation, by an intermediate platform, or by the exchange, and each has a different resolution path. Grouping rejections by their message text rather than by the surface symptom speeds up diagnosis considerably. The sections below are organized around specific rejection messages for exactly that reason.
Price Increment Rejections
What "not rounded to a valid price increment" means
Each instrument has an exchange-defined minimum tick size, and limit or stop prices must be exact multiples of that tick. A mismatch between the tick size your strategy uses and the tick size TradeStation's data feed supplies causes this rejection. The order is mathematically correct from your strategy's perspective but invalid at the exchange level.
Resolution path for tick-size errors
This error is a data discrepancy, not a strategy logic error. Changing your strategy's price rounding to match the tick TradeStation reports is a workaround, not a permanent fix, because the underlying data disagreement remains. If the tick data TradeStation supplies appears wrong for the instrument, escalate to TradeStation support rather than adjusting the strategy to compensate for bad data.
Asset Class Errors
Broker does not support asset class
Not every broker supports every asset class, and attempting to route an order to a broker that lacks support for that class produces a hard rejection that cannot be configured away. The TradeStation connection supports stocks, options, index options, and futures but not crypto. If your strategy trades an asset class TradeStation does not carry, you need a different broker for that strategy, not a different configuration.
Asset class not enabled on your account
Even when TradeStation supports an asset class, your specific account must have that class enabled before orders are accepted. Futures options on TradeStation require a dedicated futures options account and a minimum start-of-day equity of $5,000 to place opening transactions.1 If the relevant asset class is not enabled on your account, the fix is in account settings, not in strategy settings.
Account Selection Errors
"You are required to select at least one account"
This error appears when editing a connected broker and no live or paper account is selected. For a newly created TradeStation broker connection, TradeStation requires up to 24 hours to fully provision the account before it will be visible for selection. Attempting to save the broker connection before provisioning completes will produce this error regardless of how the connection is configured.
Restrictions that require a phone call
TradeStation does not automatically reset account restrictions after they are applied.1 You must call the Futures Trade Desk to lift a restriction. Until that call is made and the restriction removed, automated orders sent to that account will be rejected regardless of order or strategy configuration.
Extended Hours Order Rejections
Why market orders fail outside regular hours
Market and stop orders are not accepted during pre-market or after-hours sessions.1 Only limit orders with a time-in-force of Day+, GTC+, or GTD+ are valid outside regular hours. Sending a market order with an extended-hours time-in-force will be refused before it reaches the exchange, which is why the rejection message references order type rather than price or quantity.
Limit order rules in extended sessions
The limit order protection rules that apply during the 9:30 AM to 4:00 PM session do not apply the same way in extended hours.1 It is possible for an order to trade at a price above a resting sell limit order without that order receiving an execution. Liquidity is also lower in extended hours, which widens bid-ask spreads and increases price volatility, affecting fill probability for limit orders even when they are correctly formatted.1
Buying Power and Margin Rejections
Intraday vs. overnight buying power
Intraday buying power equals four times margin excess when margin equity is at or above $2,000.1 Below that threshold, both intraday and overnight buying power drop to one times margin excess. An order that exceeds available buying power is rejected at submission, not after a delay, so the rejection message will reference buying power or margin rather than order validity.
Margin calls and forced liquidation
A margin call can occur intraday or overnight as soon as account equity falls below the required level for open positions.1 TradeStation may liquidate positions to meet a margin call without prior notice, and an open margin call can block new order entry until it is resolved.1
Futures positions have a separate dynamic worth understanding. Because certain electronic index contracts can be traded at the day-trade margin rate, your account may show a negative purchasing power figure without that indicating a margin call.1 Confirm whether a margin call is actually active before assuming rejected orders are margin-related.
Orders Stopped Before Reaching TradeStation
Trading windows and allowed-sides filters
A trading window configured in strategy subscription settings will block a signal that arrives outside the permitted time range, producing no order at all rather than a rejection from TradeStation. An allowed-sides setting that permits only buys will silently drop a sell signal without sending it to the broker. Neither of these failures appears as a TradeStation rejection because the signal never left the platform.
Signal staleness cutoffs
A rejectAfter value in the webhook payload sets a maximum signal age in seconds; signals older than that threshold are dropped before any order is sent. If the time field is missing from the payload, the staleness check uses the webhook receive time, which can cause signals to be dropped if delivery is delayed. Both outcomes look identical from TradeStation's perspective: no order arrives.
Auto-submit not enabled
If the Auto submit checkbox is not checked in strategy subscription settings, signals are logged but orders are not sent to the broker automatically. This is one of the most common causes of "nothing happened" failures where signals appear in the log but no order reaches TradeStation. The fix is a single checkbox, not a strategy or webhook change.
Paper vs. Live Behavior Differences
How TradeStation's simulator differs from live
The TradeStation SIM environment uses the same API surface as the live environment but executes against simulated accounts seeded with fake money; orders are not actually executed against real markets.2 Simulated trading on TradeStation may produce delayed fills and market data, which means paper results can differ from live execution timing.3
Switching between SIM and live endpoints
The TradeStation SIM API base URL (https://sim-api.tradestation.com/v3) differs from the live URL (https://api.tradestation.com/v3).2 Routing a live-intended order to the SIM endpoint means it will never execute against a real account. TradeStation explicitly notes it is not liable for mistakes made by applications that allow users to switch between SIM and live environments, so verifying the active endpoint before going live is essential.2
Identifying which environment is active
In TradeStation's desktop platform, all simulated account numbers begin with "SIM" and the status bar shows "Sim" when the simulator is active.3 Trade Bar and TradeManager status messages are preceded by "Simulated Acct" in simulator mode, providing a second confirmation that orders are going to the SIM environment rather than live accounts.3
Diagnostic Checklist Before Contacting Support
Signal log review
Confirm the alert fired in TradingView's Alerts log. If the signal appears on the chart or in the backtester but not in the Alerts log, the signal was never sent, and the likely cause is Pine Script repainting rather than a TradeStation rejection. Only signals that appear in the Alerts log were actually dispatched to a webhook.
After confirming the alert fired, check the strategy signals log in TradersPost to confirm the webhook was received, then click into the individual trade record for any rejection message returned by TradeStation. The signals log timestamps each inbound request and shows the broker response, so you can tell immediately whether the block was on the platform side or the broker side.
Order type and time-in-force audit
- Confirm the alert fired in TradingView's Alerts log before investigating further.
- Check the strategy signals log to verify the webhook was received and inspect the rejection message on the trade record.
- Verify the order type matches what the current session supports: market orders fail in extended hours regardless of strategy configuration.
- Check that the time-in-force sent in the webhook payload is one TradeStation accepts; unsupported values fall back to the default configured in subscription settings.
- Confirm Auto submit is checked in strategy subscription settings if signals appear in the log but no orders reach TradeStation.
- Verify the active API endpoint (SIM vs. live) if orders appear to be accepted but never execute in a real account.
- Check buying power and confirm no margin call is active if orders are rejected at submission with no other obvious cause.
If all of the above check out and orders are still being rejected, contact TradeStation support with the rejection message text and the timestamp of the failed order. The specific message text is the most useful thing you can provide.
Conclusion
Most TradeStation order rejections follow a short list of patterns: the wrong order type for the session, a price that does not match the tick increment, an account that is not provisioned or not enabled for the asset class, or a signal that was filtered out before it reached the broker. Reading the rejection message at the order level narrows the search immediately.
Bottom line takeaways:
- The rejection message text is the starting point for every diagnosis: do not change strategy settings before reading it.
- Market and stop orders are invalid outside regular trading hours; extended sessions accept limit orders with Day+, GTC+, or GTD+ duration only.
- A new TradeStation account needs up to 24 hours to provision before it can be selected for order routing.
- Account restrictions are not lifted automatically; clearing a restriction on a futures account requires a call to the Futures Trade Desk.
- Signals that never reach TradeStation, because of a trading window, an allowed-sides filter, a staleness cutoff, or a disabled Auto submit checkbox, will not produce a rejection message from TradeStation at all.
Frequently Asked Questions
Why does TradeStation reject my market order before the exchange even sees it?
Market and stop orders are not permitted during pre-market or after-hours sessions; only limit orders with Day+, GTC+, or GTD+ duration are accepted outside regular hours.1 Verify the session your alert fires in and switch to a limit order type if your strategy runs in extended hours.
How long does it take for a new TradeStation account to be ready for order routing?
TradeStation requires up to 24 hours to fully provision a new account before it becomes selectable in connected trading platforms. Attempting to connect or route orders before provisioning completes produces an account selection error.
Can I test automated TradeStation orders without risking real money?
TradeStation offers a SIM API environment that is identical to the live API but uses simulated accounts seeded with fake money and does not execute real orders.2 The SIM environment uses a different base URL than the live environment, so you must point your automation at the correct endpoint before testing. In the desktop platform, simulated account numbers begin with "SIM" and the status bar displays "Sim" when the simulator is active, giving you a clear visual confirmation of which environment is running.3
Does TradeStation automatically lift a trading restriction on my account?
No. TradeStation does not automatically reset account restrictions; you must call the Futures Trade Desk to have a restriction removed.1 Until the call is made and the restriction is lifted, all automated orders sent to that account will be rejected.
Why do my signals appear in the log but no order reaches TradeStation?
The most common cause is that Auto submit is not enabled in the strategy subscription settings, so signals are recorded but not forwarded to the broker. A trading window configuration or an allowed-sides filter can also block a signal from being sent without returning an error from TradeStation. A staleness cutoff set via the rejectAfter field will silently drop signals older than the configured threshold before any order is placed.
References
1 TradeStation FAQs
2 TradeStation API: SIM vs. Live
3 TradeStation Help: Simulated Trading
