Exchange order limit
Bybit caps the number of simultaneously active orders at 500 per account. Every grid level and every DCA averaging order takes one place. When there is little room left, the bot warns you in advance, and it will not place new orders that do not fit into the reserve.
What it is
- The limit of 500 active orders counts for the whole account (for one API key pair), not for a pair. Three Grid bots on different pairs share one and the same limit.
- The bot keeps a reserve of 20 orders: if new orders do not fit into it, they will not be placed.
- The warning arrives at 80 % of the limit and repeats no more often than once every 30 minutes: “⚠️ You are using 410 of 500 active orders on the exchange (82%). At 500 the exchange will start rejecting new orders. Consider stopping some Grid/DCA bots.”
- Separately, the exchange caps the number of orders on a single pair. For large grids this is solved by the active window: when you create a Grid bot, the bot suggests it itself — “you have 150 levels — this is a large Grid. Consider enabling active window (50 is recommended) to stay within the exchange's limit (500 orders/symbol)”.
Where it is in the bot
The warning arrives in the notification bot. There is no separate screen for the limit — it is spent by the bots:
- Grid: the number of levels (🪜 Grid Bots → the bot) and the size of the active window;
- DCA: the Active entry orders parameter (📉 DCA Bots → the bot → settings) — how many averaging orders to keep on the exchange at the same time; the rest wait and are placed as fills happen.
Example with the numbers
| Bot | Orders on the exchange |
|---|---|
| Grid BTCUSDT, 120 levels, no active window | 120 |
| Grid ETHUSDT, 120 levels, no active window | 120 |
| Grid SOLUSDT, 120 levels, no active window | 120 |
| DCA with 20 active entry orders | 20 |
| Total | 380 of 500 (76 %) |
For simplicity we assume every level is occupied by an order; in reality part of the grid levels are empty at any moment (a Long grid starts with orders below the price only), so the real load is lower. There is no warning yet. Add a fourth grid of 60 levels — 440 orders, 88 %: “⚠️ You are using 440 of 500 active orders on the exchange (88%)…” arrives. A fifth grid of 50 levels will no longer fit: 440 + 50 = 490, while with the reserve only 500 − 20 = 480 are available.
If you turn on an active window of 50 levels for the first three grids, they will take 150 orders instead of 360, and the total load drops to 230 (46 %).
What to do when you get the warning
- Stop or pause part of the Grid and DCA bots — the fastest way.
- Turn on the active window for large grids, or reduce the number of levels when you recreate them.
- Reduce Active entry orders for DCA bots.
- Do not create new bots until the load goes down.
Limits and allowed values
| Parameter | Value |
|---|---|
| Active order limit | 500 per account (one API key pair) |
| The reserve the bot keeps | 20 orders |
| Warning threshold | 80 % of the limit |
| How often the warning repeats | No more often than once every 30 minutes |
| Grid levels | 2–200 |
| Grid active window | 1–200 or all levels |
| Active entry orders for DCA | 1–20 |
Common mistakes and what the bot says
- “⚠️ Exceeded the limit of simultaneous limit orders for this symbol on the exchange. What to do: wait for some orders to fill/cancel or reduce the number of levels. The trade state is reconciled with the exchange automatically.” — you hit the limit on a single pair, not on the account.
- “⚠️ Exceeded the limit of conditional (stop) orders for this symbol. What to do: cancel some conditional orders or wait for them to trigger, then retry.” — too many stop orders on one pair.
- A Grid bot was paused with the reason “3 consecutive order placement errors (last: …)” — if the last error is about the order limit, free it up and tap ▶️ Resume.
