Delayed start by price

A trigger is a price at which the Grid bot will start placing orders. Until the price reaches it, the bot is created but does nothing on the exchange.

What it is

Without a trigger the bot activates right after the confirmation. With a trigger it goes to the status “Waiting trigger”, places no orders at all and watches the price. As soon as the price reaches the set level, the usual activation begins: “⏳ Grid … Placing N orders on the exchange…”.

The bot picks the trigger direction itself, from the current price:

Trigger versus the current price	Direction	When it fires
above	“ABOVE (above current)”	when the price rises to the level
below	“BELOW (below current)”	when the price falls to the level

If at the moment of creation the price is already on the right side of the trigger, the bot activates instantly. It works both on spot and on futures.

Where it is in the bot

Main menu → 🪜 Grid Bots → ➕ Create Grid Bot → the confirmation screen → the button 🎯 Set trigger. After you enter the price the button changes to 🎯 Trigger: 65000, and the summary gains the line “🎯 Trigger: 65000 (ABOVE (above current))”. Without a trigger the summary says: “🎯 Trigger: not set (bot activates immediately)”.

In the card of a created bot there is the 🎯 Activate now button — it starts the bot without waiting for the price. The trigger cannot be removed from the card: either wait or activate by hand.

How to set it up

1. Tap 🎯 Set trigger. The bot shows the screen “🎯 Trigger price for Grid bot”: “Enter a price at which the bot will activate. Direction (above/below current) is detected automatically. If no trigger is needed — press 'Back', the bot will activate immediately on creation.”
2. Send the price as a number, for example 65000. The answer: “✅ Trigger set: price 65000, direction ABOVE (above current) (current: 63000).”
3. Changed your mind — tap 🗑️ Remove trigger (the button appears after the price is entered): “✅ Trigger removed. Bot will activate immediately.”
4. Confirm the creation. The bot goes to the status “Waiting trigger”; there will be no orders on the exchange.

Example with a calculation

The current BTCUSDT price is 63,000. You are preparing a Long grid 60,000 — 66,000 of 11 levels.

• Trigger 61000 → direction BELOW. The bot will wait for a pullback to 61,000 and only then place the buys; until that the grid amount stays free on the account.
• Trigger 65500 → direction ABOVE. The bot waits for growth: handy if you want the grid to switch on after the move is confirmed.
• Trigger 63000 at a price of 63,000 → the price is already on the right side, the bot activates immediately, as if there were no trigger.

The bot checks the start conditions twice: at the confirmation and at the moment the trigger fires. If something changed while it was waiting — for example, the pair was taken by another bot or the position mode was changed on the exchange — the activation will not go through, and you will get a notification (see below).

Limits and allowed values

Parameter	Value	Note
Trigger price	a positive number	the direction is chosen automatically
Where it works	Spot and Futures
Changing it after creation	not possible	only 🎯 Activate now
Orders in the status “Waiting trigger”	not placed	the grid amount is not reserved on the exchange

Common mistakes and what the bot says

• “❌ Invalid number. Enter a positive price (e.g. 50000).” — letters, a comma or a negative value.
• “⚠️ Could not fetch current price. Defaulting direction to BELOW.” — the bot could not read the price of the pair at the moment of input; check that the trigger really is below the market, otherwise remove it and set it again.
• “⚠️ Grid BTC grid — trigger fired, but activation was blocked. Grid bot requires One-Way position mode… The bot keeps waiting for the trigger. Switch the account to One-Way mode and it will start on the next trigger hit (or launch it manually).” — while the bot was waiting, the position mode was changed on the exchange. Bring One-Way back and tap 🎯 Activate now — see One-Way position mode.
• “⚠️ Grid BTC grid — trigger fired, but activation was blocked. … Fix the issue and it will start on the next trigger hit (or launch it manually).” — another check did not pass, for example the pair was taken by another bot; the reason is given on the second line of the notification.