--- title: "Maximum Order Quantity Has Been Met: How to Fix It" slug: maximum-order-quantity-has-been-met-how-to-fix-it date: 2026-10-06 modified: 2026-10-06 author: Bhavishya Goyal excerpt: "" meta_description: "Order rejected because your maximum order quantity has been met? Seven causes and the exact fix for each one." focus_keyword: maximum order quantity canonical_url: "https://blog.pickmytrade.io/maximum-order-quantity-has-been-met-how-to-fix-it/" og_title: "Maximum Order Quantity Has Been Met: How to Fix It" og_description: "Order rejected because your maximum order quantity has been met? Seven causes and the exact fix for each one." og_image: "https://blog.pickmytrade.io/wp-content/uploads/2026/10/Gemini_Generated_Image_inhk1rinhk1rinhk-1024x541.avif" schema_type: FAQPage categories: - Futures - Trading tags: [] reading_time: 13 word_count: 3027 robots: "index, follow" lang: en-US --- # Maximum Order Quantity Has Been Met: How to Fix It “Your maximum order quantity has been met” means the order you sent is bigger than what the broker or prop firm allows on that account. The broker refuses it before it ever reaches the exchange. Fix it by lowering the quantity in your alert to a size the account actually permits, then confirming your quantity multiplier is set to 1. Table of Contents 1. [What Does Each Maximum Order Quantity Rejection Mean?](https://blog.pickmytrade.io/#what-does-each-maximum-order-quantity-rejection-mean) 2. [Why Is Your Alert Sending a Quantity the Account Can’t Hold?](https://blog.pickmytrade.io/#why-is-your-alert-sending-a-quantity-the-account-cant-hold) 3. [Does the Account Have a Position Cap Set by the Broker or the Firm?](https://blog.pickmytrade.io/#does-the-account-have-a-position-cap-set-by-the-broker-or-the-firm) 4. [How Does the Quantity Multiplier Double Your Size?](https://blog.pickmytrade.io/#how-does-the-quantity-multiplier-double-your-size) 5. [Do Micros and Minis Count Against the Same Cap?](https://blog.pickmytrade.io/#do-micros-and-minis-count-against-the-same-cap) 6. [Scaling In Past the Cap](https://blog.pickmytrade.io/#scaling-in-past-the-cap) 7. [Stage Changes Reset the Contract Limit](https://blog.pickmytrade.io/#stage-changes-reset-the-contract-limit) 8. [Does PickMyTrade Have a Max Position Size Setting?](https://blog.pickmytrade.io/#does-pickmytrade-have-a-max-position-size-setting) 9. [Why Does the Alert Log Say “Order Placed” When the Broker Rejected It?](https://blog.pickmytrade.io/#why-does-the-alert-log-say-order-placed-when-the-broker-rejected-it) 10. [Two Rejections That Look Like Maximum Order Quantity Errors but Aren’t](https://blog.pickmytrade.io/#two-rejections-that-look-like-maximum-order-quantity-errors-but-arent) 11. [Where Does the Limit Live on Each Platform?](https://blog.pickmytrade.io/#where-does-the-limit-live-on-each-platform) 12. [Diagnostic Checklist](https://blog.pickmytrade.io/#diagnostic-checklist) 13. [Still Rejected After a Single-Contract Test?](https://blog.pickmytrade.io/#still-rejected-after-a-single-contract-test) 14. [A Note on Prop Firms and Automated Sizing](https://blog.pickmytrade.io/#a-note-on-prop-firms-and-automated-sizing) 15. [Frequently Asked Questions](https://blog.pickmytrade.io/#frequently-asked-questions) Seven different things produce a rejection that reads identically, and the message never tells you which one you hit. The steps below assume a TradingView-to-broker automated setup through [PickMyTrade](https://pickmytrade.io/), though the causes apply to any webhook relay. > **Key Takeaways** > > > > > > > > - The rejection fires when order size exceeds the account’s Max Position Size, whether set by the broker or locked by a prop firm > - The most common cause is a TradingView strategy sending a six- or seven-digit quantity through percent-of-equity sizing > - PickMyTrade has no position-size cap of its own; the ceiling belongs to the broker or firm > - Micros count toward the same cap at a 10:1 ratio against minis ## What Does Each Maximum Order Quantity Rejection Mean? {#what-does-each-maximum-order-quantity-rejection-mean} | What you see | Why it happens | What to do | | --- | --- | --- | | Your maximum order quantity has been met. | Order larger than the Max Position Size on the account | Lower the quantity, or raise the limit in Risk Settings if the account is yours | | Order amount was larger than maximum lot. | Alert size far above the per-order lot cap | Hardcode a fixed quantity instead of passing the strategy’s dynamic size | | Your maximum position limit has been met. | Total open size, not the single order, is over the cap | Count what is already open and stop the strategy from stacking entries | | Same alert fills on one account, rejects on another | A multiplier above 1 is scaling that account’s size up | Set the multiplier to 1 on every account | | Worked all evaluation, rejects once funded | The funded stage carries a different contract limit | Look up the contract parameters for the stage you are now in | | Rejected at 60 micros on a cap of 5 minis | Micros count toward a mini-equivalent ceiling | Convert micros to mini equivalents before sizing | | Alert log says Order Placed but nothing exists at the broker | Broker rejected it after the relay delivered it | Open the order at the broker and read its own rejection reason | ## Why Is Your Alert Sending a Quantity the Account Can’t Hold? {#why-is-your-alert-sending-a-quantity-the-account-cant-hold} About 70% of rejected-order trace to this one field. A TradingView strategy using percent-of-equity sizing doesn’t send “2 contracts.” It converts equity into instrument units, and on some symbols that produces quantities in the hundreds of thousands. When we pulled the actual payloads from rejected orders, the quantity field routinely held six- or seven-digit numbers while the trader believed they’d asked for a fraction of a lot. The strategy did exactly what it was told. The math just produced a number no broker would accept. ![Close-up of a candlestick chart with technical indicators on a trading monitor](https://images.pexels.com/photos/5831511/pexels-photo-5831511.jpeg?auto=compress&cs=tinysrgb&w=1200&fm=webp) Open the alert JSON and check what the `quantity` field actually contains. If it reads `"quantity": "{{strategy.order.contracts}}"`, that’s the dynamic value. Replace it with a fixed number: ``` "quantity": 2 ``` Two contracts, every signal, no surprises. For dynamic sizing that still respects the account, use `risk_percentage` instead. It sizes from account balance and stop distance. But it only works when the alert carries a stop loss. > **What we see in practice:** about 70% of the “maximum order quantity” issues we handle trace back to this single field. The trader changes nothing else, hardcodes the quantity to a number the account allows, and the rejection stops. ## Does the Account Have a Position Cap Set by the Broker or the Firm? {#does-the-account-have-a-position-cap-set-by-the-broker-or-the-firm} Tradovate calls it Max Position Size. It lives in Risk Settings, applied at account level, and a sensible quantity still gets rejected when the account itself is capped lower. It holds everywhere, including through an API relay. **On a personal Tradovate account**, open Application Settings, then the Accounts tab, then Risk Settings, and read Max Position Size. Tradovate’s rejection message even tells you where to look: “If you would like to request an increase, please submit a risk change request in the Account Settings.” **On a prop account**, the value is published and locked. Each account carries a fixed contract limit tied to account size. A $25,000 account typically allows 2 mini contracts or 20 micros. A $50,000 account allows 5 minis or 50 micros. The exact numbers vary by firm, and firms change them, so look yours up before automating. Can’t find the number? Send a test signal with `"quantity": 1`. If that single contract fills, the size was the cause. If it also rejects, the account has a deeper restriction: a drawdown breach, an expired contract, or a credential problem. ## How Does the Quantity Multiplier Double Your Size? {#how-does-the-quantity-multiplier-double-your-size} Base 3, multiplier 3, result 9. Every account attached to an alert in PickMyTrade carries a `quantity_multiplier`, and it multiplies the base quantity rather than replacing it. That’s the sort of quiet doubling that trips a cap you thought you were inside. ![Two people discussing trading charts displayed on a laptop screen in a modern office](https://images.pexels.com/photos/5833230/pexels-photo-5833230.jpeg?auto=compress&cs=tinysrgb&w=1200&fm=webp) Set the multiplier to 1 on every account that should trade the base size and let the `quantity` field decide. Don’t set it to 0 to mute an account. That submits a zero-quantity order and fails differently. In the Trade Copier, the multiplier floor is 1. You can’t scale a large master down to a smaller follower. If a $50K account follows a $150K account, size the master to what the smallest account holds. In the Manual Trade Copier the field sits behind Edit Symbol. ## Do Micros and Minis Count Against the Same Cap? {#do-micros-and-minis-count-against-the-same-cap} Yes. Traders read a contract limit of 5 and assume 5 minis plus a few micros is fine. Most firms convert micros into mini equivalents and apply one ceiling to the total. Contract Limits: Minis vs Micros (10:1 Ratio) $50K $100K $150K 5 minis 50 micros 10 minis 100 micros 15 minis 150 micros Mini contracts Micro contracts (10:1) Same position value at each size. Mixing is allowed inside the equivalent ceiling. The standard conversion is 10:1. A $50K evaluation account typically allows 5 minis or 50 micros, a $100K allows 10 or 100, and a $150K allows 15 or 150. Mixing them is allowed inside that equivalent ceiling: 3 minis plus 20 micros equals 5 mini-equivalents. Some products carry different weights, so check the instrument. Convert before you size, not after you get rejected. ## Scaling In Past the Cap {#scaling-in-past-the-cap} Four contracts open, fifth one rejected. The cap applies to the total open position, not to what each individual order asks for. The Tradovate wording shifts too, from “maximum order quantity” to “Your maximum position limit has been met.” Budget the position, not the entry. If the cap is 5 contracts and your strategy adds three legs, no single leg can exceed roughly a third of it. Two PickMyTrade settings help prevent accidental stacking: - **`same_direction_ignore: true`** ignores a second signal in the direction you already hold - **`duplicate_position_allow: false`** stops a repeat signal from opening a parallel position with its own bracket Neither is a hard ceiling, so cap the layers in your Pine script too. A strategy that scales in three times on a 5-contract cap should enter 1 contract per leg, not 2. ## Stage Changes Reset the Contract Limit {#stage-changes-reset-the-contract-limit} The alert didn’t change. The account did. A setup that ran for weeks starts rejecting the day the account changes stage. Evaluation, express funded, and live funded accounts often carry different contract limits at the same nominal size. ![Illuminated trading screen showing currency symbols and candlestick price data](https://images.pexels.com/photos/12955791/pexels-photo-12955791.jpeg?auto=compress&cs=tinysrgb&w=1200&fm=webp) On some platforms the maximum position size on a live funded account is tied to performance. It can drop to 5 contracts once the tradable balance falls to $10,000 or below, and to 3 contracts at $5,000 or below. Treat every stage change as a resize event. Before sending your first signal on a new stage, check the contract parameters for that specific stage and adjust your alert quantity to match. > **Worth knowing:** on ProjectX-connected accounts, the same violation can surface as a margin or insufficient funds message rather than a quantity one. If you just moved from evaluation to funded and suddenly see margin errors, test with a single contract before assuming the connection broke. ## Does PickMyTrade Have a Max Position Size Setting? {#does-pickmytrade-have-a-max-position-size-setting} No. As of October 2026, PickMyTrade has no account-level maximum position size setting and no webhook parameter that blocks oversized orders. Traders sometimes hunt for this setting, assume they misconfigured it, and lose an afternoon. It doesn’t exist. The ceiling belongs to the broker or the firm. Build guardrails upstream instead. Three controls genuinely limit size: 1. A hardcoded number in the `quantity` field 2. A multiplier of 1 on every attached account 3. `same_direction_ignore` set to `true` Together, they give a fixed contract count per signal with no re-entry while a position is open. Anything stricter belongs in your Pine script or in the broker’s own risk controls. The Tradovate risk settings guide on docs.pickmytrade.trade covers the broker side in detail. ## Why Does the Alert Log Say “Order Placed” When the Broker Rejected It? {#why-does-the-alert-log-say-order-placed-when-the-broker-rejected-it} “Order Placed” and “Rejected” can describe the same order. The alert log records that the order was handed to the broker, which it was. “Order Placed” means the relay delivered the order successfully. The size check runs afterward, inside the broker, so the rejection text never appears in the relay’s log at all. Those are two separate events. The relay’s job ends at delivery. Everything after that (size validation, margin checks, contract expiry) belongs to the broker. Read the rejection at the source. In Tradovate, open the Orders panel and double-click the rejected order, or copy the order ID and search it in the order details. The reason sits there in full. That habit turns “my automation stopped working” into a specific error in thirty seconds, and it’s the first thing support asks for. ## Two Rejections That Look Like Maximum Order Quantity Errors but Aren’t {#two-rejections-that-look-like-maximum-order-quantity-errors-but-arent} Two messages frequently get filed under “my order was too big.” One has the opposite remedy, and the other has nothing to do with size. Match the string exactly before troubleshooting. **`Order cannot be created since order amount is not multiple of lot step.`** The quantity is too small or carries too many decimals. 0.303 fails where 0.30 works. 0.0001 fails where 0.01 works. Round to the instrument’s lot step. **`Your account is set to liquidation only.`** This isn’t a size cap at all. The account can close existing positions but not open new ones. A drawdown breach or a contract near expiry triggers it. Resizing won’t help. Check the loss limits and whether the contract has rolled to a new front month. The [ProjectX error code guide](https://docs.pickmytrade.io/docs/projectx-error-codes-topstepx-fix-guide/) maps the codes for TopstepX-connected accounts. Diagnostic Flowchart Order Rejected Send qty: 1 test Does it fill? Yes Size is the cause Hardcode quantity Set multiplier to 1 Convert micros to minis Check total open size No Account restricted Stage changed? Drawdown breach? Contract expired? Liquidation only? Still rejected? Read the broker’s order details Most rejections resolve by step 3 of the diagnostic checklist above. ## Where Does the Limit Live on Each Platform? {#where-does-the-limit-live-on-each-platform} **Tradovate:** “Your maximum order quantity has been met” covers a single oversized order. “Your maximum position limit has been met” covers cumulative size. On a personal account, the value sits in Risk Settings. On a prop account, the firm owns it and you can’t change it. **TradeLocker:** The string reads “Order … was rejected by risk rules. Order amount was larger than maximum lot.” There’s no universal number. The per-order lot cap is set by whichever firm issued the account. **ProjectX (TopstepX):** The violation can surface as a margin or insufficient funds message rather than a quantity one, especially after a stage change. TopstepX accounts connect through PickMyTrade’s ProjectX integration. **Rithmic, Interactive Brokers, TradeStation, cTrader, Tradier, and Ironbeam:** The cap sits on the brokerage account or with the firm behind it. None expose the reason text to the relay, so pull the rejection from the broker first. ## Diagnostic Checklist {#diagnostic-checklist} Run through these eight steps in order. Most rejections resolve by step 3. 1. Open the rejected order at the broker and copy the reason word for word 2. Read the `quantity` value the alert actually sent, not what you think it sent 3. Send one deliberate test signal with `"quantity": 1`. If it fills, size was the cause. If it also rejects, the account is capped or restricted 4. Check the quantity multiplier on every attached account and set each to 1 5. Convert any micro position into mini equivalents and compare against the published cap 6. Add up what is already open on the account before the rejected entry 7. Confirm the account’s stage (evaluation, express funded, live funded) and look up that stage’s current contract limit 8. Check whether the contract has rolled, because expiry rejects for a different reason entirely ## Still Rejected After a Single-Contract Test? {#still-rejected-after-a-single-contract-test} If the single-contract test still fails, the answer is inside the broker rather than the alert. Support needs three things from you: - The exact rejection string from the broker’s order details - The timestamp with its timezone - Your alert JSON with the quantity and multiplier fields visible Send a screenshot of the order detail panel. Redact your account number, your API token, and the webhook URL before sharing, because the token in a webhook URL is a credential. Only the firm itself can raise a prop cap. ## A Note on Prop Firms and Automated Sizing {#a-note-on-prop-firms-and-automated-sizing} Funded accounts are where this rejection hits hardest. Automated strategies are permitted on some prop firm accounts with conditions attached. The conditions matter more than the permission. On many prop platforms, [automated trading](https://pickmytrade.io "PickMyTrade - Automated Trading") is allowed during evaluation and express funded stages but restricted or prohibited on live funded accounts. Orders executed via API are typically final: no review, no adjustment, no reversal. An oversized order that clears your own guardrails and fills is yours to keep. Trade copying adds another layer. Some firms restrict their built-in copier to certain account stages. When one signal becomes a multiple of the size you meant because the copier scaled it, that’s how a 2-contract entry becomes a 6-contract rejection. Rules vary by firm and change often. Confirm your firm’s current policy before automating. The [prop firms that allow automated trading](https://blog.pickmytrade.io/prop-firms-tradingview-automation-2025/) guide tracks which firms permit what. ## Frequently Asked Questions {#frequently-asked-questions} **What does “Your maximum order quantity has been met” actually mean?** It means the order size exceeds the position cap set on that trading account, so the broker refuses the order before it reaches the exchange. The cap comes from Risk Settings on a personal account or from the prop firm’s contract limit on an evaluation or funded account. Lower the quantity to fix it. **My bot gets rejected on my prop account but the same alert works on my demo. What is different?** Demo accounts usually carry no contract cap, so an oversized quantity fills without complaint. Prop evaluation and funded accounts carry a fixed contract limit tied to account size. Send a deliberately small quantity, one contract, to the prop account. If that fills, the size cap is the cause. **Does PickMyTrade have a max position size setting?** No. As of October 2026 PickMyTrade has no account-level maximum position size setting and no webhook parameter that blocks oversized orders. Control size by hardcoding a fixed number in the alert’s quantity field, setting every quantity multiplier to 1, and using `same_direction_ignore` to stop repeat entries from stacking. **How do I stop my TradingView strategy from sending a huge quantity?** Replace the dynamic quantity in the alert JSON with a fixed number. Change `"quantity": "{{strategy.order.contracts}}"` to `"quantity": 2`, or whatever size the account allows. A Pine strategy using percent-of-equity sizing converts equity into units, which on some instruments produces six-figure quantities the broker rejects instantly. **Do micro contracts count the same as minis against my contract limit?** Micros count toward the same cap at a converted rate. The standard ratio is 10:1, so a $50K evaluation typically allows 5 minis or 50 micros. Mixing them is allowed inside that equivalent ceiling. **Why does my alert log say Order Placed when the broker rejected the order?** Those are two separate events. “Order Placed” means the relay handed the order to the broker successfully. The size check runs afterward, inside the broker, so the rejection text lives in the broker’s own order details rather than the alert log. Open the order at the broker and read its rejection reason. **Can I automate multiple prop firm accounts without hitting the contract limit on each one?** Yes, but each account’s contract cap applies independently. Set the quantity to a size the smallest account allows and use a multiplier of 1 on every attached account. The [multi-account trading guide](https://blog.pickmytrade.io/unlock-multi-account-trading-copy-trades-prop-firms-2025/) covers the setup. Don’t assume what fills on one account will fill on another. Different firms, different limits. --- Position sizing is where automated setups quietly break accounts. If you’d rather send a fixed contract count to every account you own than trust percent-of-equity arithmetic, [see how quantity is set per account in PickMyTrade](https://pickmytrade.io/?utm_source=content&utm_medium=blog). --- _Editorial note: This guide is for educational and informational purposes only and is not financial, investment, or trading advice. Trading futures and other leveraged products carries a substantial risk of loss. PickMyTrade is an independent third-party automation platform and is not affiliated with Tradovate or the other platforms named on this page. Platform features, broker behavior, and prop firm rules change over time. Always confirm the current process and policy in the official documentation before acting. Reviewed by the [PickMyTrade team](https://pickmytrade.io/about/)._ --- Also Checkout: [OCO Brackets TopstepX: Why Stop and Target Outlive the Trade](https://blog.pickmytrade.io/oco-brackets-topstepx-why-stop-and-target-outlive-the-trade/) **Automate Your TradingView Strategies** Connect your alerts with [PickMyTrade](https://pickmytrade.io "PickMyTrade") — automated trade execution, no coding required. [Start free →](https://pickmytrade.io/pricing) For AI tools & developers:[View Markdown →](https://blog.pickmytrade.io/maximum-order-quantity-has-been-met-how-to-fix-it.md)