Entry quantity reduced from {{ requestedQuantity }} to {{ reducedQuantity }} so your {{ tickerRoot }} exposure stays within the maximum of {{ maxQuantity }} configured for this account.
This message indicates that TradersPost trimmed the entry quantity so the resulting holding stays within the maximum you set for that ticker. It appears when the Ticker Quantity Limits row for the symbol is set to Reduce to max and a quantity-based single-leg order would have gone past the maximum. The trade continues with the reduced quantity instead of being blocked.
Set those maximums under Ticker Quantity Limits on the broker account, separately for live and paper. Enter underlyings, futures roots, and crypto pairs — for example SPY, NQ, or BTC-USD — not individual option or futures contracts, and not a bare crypto base like BTC. The maximum applies to the underlying: everything you hold on SPY counts toward the SPY limit, whatever the expiration or strike, and every NQ contract month counts toward NQ. Crypto limits are per pair. Long and short both count rather than cancelling out, and shares are counted separately from contracts.
For example, with a SPY maximum of 4 and 3 already open, an order for 2 is reduced to 1 so the resulting holding lands on 4. The trade message reports the original requested quantity, the reduced quantity that was submitted, and the configured maximum.
When there is no room left under the maximum — you already hold at or past the cap, or sibling instruments already fill it — Reduce to max cannot trim the order and the trade is rejected with the Max Quantity Per Ticker message instead. Dollar-amount orders without a known share quantity and multi-leg trade plans also reject on breach rather than reduce.
Free 7-day trial
Set-up in 3 minutes
Paper account for testing