The practical answer: stop submitting orders, save the exact rejection, and identify whether the block comes from the account, the market, the order settings, billing, or a wider platform incident. A rejected order is not proof of an outage. It may be the expected result of a loss-limit lock, closed market, position-size rule, personal risk setting, inactive subscription, or an account selected in the wrong state.
Do not place a smaller “test” order while the cause is unknown. Repeated attempts can create new fills, complicate the order history, or weaken an exception review. Preserve the first clean evidence, then work through the checks below.
The seven-step rejected-order checklist
1. Freeze the facts before changing anything
Record the firm, platform, exact account name, account stage, symbol, contract month, side, quantity, order type, price, time zone, and rejection text. Save the order ID if the platform created one. Capture the account status, balance, open positions, working orders, and current rule thresholds in the same minute.
Topstep's current troubleshooting guidance asks traders to provide specific order IDs rather than an entire CSV. Its support page also asks for timestamps, products, screenshots, or screen recordings. That evidence is most useful before a refresh, reconnect, or later trade changes the visible state.
2. Confirm the selected account and account state
Start with the account selector, not the chart. Verify that the order ticket is attached to the intended evaluation, simulated-funded, or live account. Then read the firm's dashboard state exactly as shown: active, temporary liquidation, liquidation-only, blocked, ineligible, closed, or another named state.
Topstep lists a breached Maximum Loss Limit, a triggered Personal Daily Loss Limit, and other risk controls among common reasons orders are rejected. Its TopstepX guide also says a follower account can have disabled direct trading while it remains connected to a trade copier. Tradeify says an account that cannot place trades may be in Liquidation-Only mode after touching a Daily Loss Limit or drawdown threshold; a Daily Loss Limit can reset next session, while a drawdown breach may be permanent.
Do not assume every lock clears overnight. The label and the exact product policy control.
3. Check the firm's permitted time and the contract's market state
An order can be correctly rejected even when the platform is healthy. Compare the timestamp with the firm's own trading window, the contract's exchange session, daily maintenance, holiday hours, and any product-specific pause or early close.
Topstep's current trading-hours page says positions must be closed by 3:10 PM CT each weekday and trading resumes at 5:00 PM CT, with earlier closes for some agricultural products. Its troubleshooting page lists orders outside permitted hours and holiday closures as rejection causes. A quote on the screen does not prove the market is open for order entry.
Use the platform-status pre-trade checklist for the full firm-platform-exchange-account sequence. Here, the question is narrower: did this order arrive during a time or market state in which the firm permits it?
4. Recalculate the resulting position, not just the new order
Check the account's maximum position size, any product conversion between minis and micros, current open positions, pending entries, trade-copier followers, scaling tier, and personal contract limit. The relevant number is the position that would exist after the order fills.
Topstep lists exceeded maximum position size as a rejection cause. TopstepX also lets a trader set stricter personal contract limits; orders beyond those limits are rejected. A follower account may have a different scaling state or be removed from a copier when scaling no longer matches the leader.
Pending orders matter. A working entry on another chart, DOM, or copied account can consume capacity even if the trader is looking only at the new ticket.
5. Inspect order-specific controls
Read the platform message instead of translating every failure into “size.” Verify the contract month, order type, stop or limit side, bracket distance, price increment, and any personal trade limit or lockout.
TopstepX currently requires auto-OCO bracket values to produce a stop or target at least four ticks from entry; an invalid dollar value can reject the order. It can also reject new orders after a personal contract or trade limit is reached. A daily risk lock or manual lockout can be intentionally irreversible until its published release time.
If the platform provides an exact reason, preserve it. Do not repeatedly edit settings until the message disappears, because that erases the clean sequence support needs to review.
6. Verify credentials, subscription, and account lifecycle
A platform can be operational while one login or account is not entitled to trade. Check for an expired or cancelled evaluation, past-due subscription, newly passed account awaiting activation, payout-processing hold, wrong credentials, or an account that has not completed its lifecycle transition.
Topstep names an inactive subscription as a cause of rejected orders. Its troubleshooting guidance also tells traders to confirm the correct credentials and account. Treat the firm dashboard—not a cached platform tab—as the source for whether that specific account is active.
7. Compare official status sources, then escalate once
Only after the account, time, size, order, and subscription checks are complete should you test the incident hypothesis against first-party status pages. Compare the firm's status page with the execution platform and exchange state. If one layer reports degraded service, or if first-party signals conflict, stop trading and save both states.
At the September 28 verification, Tradovate listed all monitored execution, risk, market-data, evaluation, funding, payment, and named prop-firm connections as up. TradingView reported all systems operational. Topstep's status page still contained a contradiction from its September 22 incident: the narrative said trading was restored while the incident remained unresolved and TopstepX was still shown as degraded in the current record. That is a reason to preserve exact signals, not to infer either a new outage or complete recovery.
Fast diagnosis table
| What you see | Likely lane | Evidence to save | Safe next step |
|---|---|---|---|
| Liquidation-only, temporary liquidation, blocked, or ineligible | Account or risk control | Dashboard status, thresholds, P&L, timestamp | Stop; read the exact product rule and contact the firm if the state is unexplained |
| Market closed, paused, holiday, or outside permitted time | Firm or exchange schedule | Contract, timestamp, market-state label, official hours | Wait for the permitted session; do not force a test order |
| Size, limit, or bracket error | Order or personal setting | Open position, working orders, quantity, bracket values, limit setting | Correct only after the message and current state are saved |
| Inactive, expired, cancelled, or wrong account | Subscription or lifecycle | Billing/account page, account name, stage, activation state | Resolve entitlement with the firm before trading |
| Multiple users or services report execution trouble and status is degraded | Platform incident | Order ID, status pages, account state, logs/screenshots | Stop trading and submit one complete support packet |
What not to do after a rejection
- Do not keep clicking Buy or Sell to see whether the block clears.
- Do not switch symbols and create another live exposure as a platform test.
- Do not enlarge, split, or copy the order to work around a position limit.
- Do not assume a daily lock, Maximum Loss Limit, and account closure have the same reset behavior.
- Do not edit or crop away the rejection text, timestamp, account name, or order ID.
- Do not call the event an outage until a first-party source or broader evidence supports that conclusion.
Topstep explicitly warns traders to stop trading when an issue occurs because continued trading can prevent review or approval of an exception request. That is sensible evidence hygiene beyond one firm: preserve the first event, avoid adding noise, and escalate with a complete timeline.
Build a support-ready evidence packet
Keep the packet short and chronological:
- account name, stage, and dashboard status;
- local time plus the firm's or exchange's source time zone;
- symbol and contract month;
- side, quantity, order type, and requested price;
- exact rejection text and order ID;
- open positions, working orders, and applicable size or risk limits;
- screenshots of the firm, platform, and exchange status sources;
- the last successful order and the first rejected order; and
- one sentence describing what changed between them.
Send the packet through the firm's official support channel. Avoid posting account identifiers publicly. If the issue involves an open position that cannot be managed, use only the firm's documented emergency-flatten path.
Bottom line
A rejected order is a control signal, not a diagnosis. Preserve it, then check the exact account, permitted session, resulting position size, order settings, subscription state, and first-party platform status in that order. If the cause remains unclear, stop trading and escalate once with the order ID and a timestamped evidence packet.
For adjacent workflows, use the pre-trade platform-status checklist before a session, the platform-outage evidence guide when an incident affects orders or positions, and the account-breach recovery guide after a confirmed rule failure.
Current Firm Offers and Direct Links
Open the firm in a new tab with the recorded ComparePropFirms commercial link. Use the displayed code when applicable, and confirm the final price and terms before paying.
Official sources
- Topstep: General Platform Troubleshooting — checked September 28, 2026; rejection causes, evidence requirements, order IDs, and instruction to stop trading.
- TopstepX platform guide — checked September 28, 2026; follower-account controls, bracket requirements, personal risk settings, lockouts, order log, and platform states.
- Topstep: When and What Products Can I Trade? — checked September 28, 2026; permitted session, close deadline, product-specific hours, and market-state labels.
- Topstep support — checked September 28, 2026; stop-trading guidance and support evidence.
- Tradeify common FAQs — checked September 28, 2026; Liquidation-Only state, Daily Loss Limit reset distinction, drawdown breach, close deadline, and exchange halts.
- Topstep status, Tradovate status, and TradingView status — checked September 28, 2026, 7:06 AM MDT; point-in-time incident and service states.
- CME notices and CFTC latest news — checked September 28, 2026; no broad exchange or directly applicable regulatory emergency displaced this evergreen guide.