Bot management

The bot management page is split into two parts: on the left — the bot’s parameters and state, on the right — the deals it’s currently running. All data updates in real time.

Bot ≠ Deal. Remember this from day one

The bot is a settings template (leverage, order size, SO step, martingale and so on) plus a market-watching service. The deal is a copy of the bot that went into work with the parameters as they were at the moment of opening.

So when you change the bot’s settings, already open deals keep running with the old parameters until their logical end. Only the next new deal starts with the updated settings.

The same applies to the bot toggle: «turn off the bot» does not mean «close the deals». The toggle only controls whether the bot opens new deals and reacts to user actions in the terminal. Active deals keep running.

Left part: the bot

A card with the bot’s settings as they were at the last save:

• Header — bot name, type (futures), last update time, ID, the «Disable bot» / «Enable bot» button (this is the master toggle).
• Bot state — In deal, Waiting for signal, Stopped, Error.
• Access — exchange account the bot runs on.
• Trading pairs — pairs the bot trades.
• Margin / Strategy — margin mode + direction + leverage (e.g., Cross, Short, x10).
• Open — first order parameters (300 USDT, Market), cycle limit before disabling.
• Averaging (DCA) — SO volume, step %, count limits, multipliers, grid width %, total margin vs your funds.
• Close — Take Profit parameters.
• Creation date.

Right part: active deals

The right column shows the deals the bot is currently running. Each deal is an independent copy of the bot with its parameters as of opening — it doesn’t pick up bot setting changes made afterwards.

Pair switcher and state

At the top — tabs per trading pair (if the bot runs several). Under them — the current deal card:

• Market price of the pair.
• Position volume (in coins + USDT).
• Entry price and liquidation price.
• PnL in USDT and percent.
• Deal parameters summary: open type (continuous / by signal), DCA, TP, SL.
• Bot’s trade cycle — N / limit.
• Deal progress in percent (how close to close).

Deal actions

Two buttons:

• Force-close the deal. The bot closes the position at market, removes all pending orders, the deal is marked completed. If the bot is enabled — it opens the next deal right away.
• Cancel the deal. The bot drops the deal from its control: position and orders stay on the exchange, but the bot no longer manages them. Going forward you control them manually via the terminal. If the bot is enabled — it’ll start a new deal right away, ignoring the leftover open position.

How to properly stop an active deal

Disabling the bot toggle does not close active deals — it only blocks opening new ones. But the order of actions matters:

First turn off the bot toggle, then handle the deal. Bots are extremely fast: if you close/cancel a deal while the bot is enabled, it’ll open a new one before you can reach the toggle.

After disabling the bot:

• Finish completely. Click «Force-close the deal» — the bot closes the position and removes all orders. The deal is done.
• Take over manually. Click «Cancel the deal» — the bot lets go, position and orders stay on the exchange. Manage further via the terminal.

Deal orders

A table with limit orders the bot has placed in the orderbook for the current deal:

• TP — Take Profit order.
• SO — Safety Order (for averaging).
• Status — placed, filled, cancelled.
• Price, volume, placement time.

At the top — counters: Filled / Placed / Total SOs / Re-grid.

Recent actions

A log of events on the selected pair in reverse chronological order: position opening, placing / cancelling / triggering orders, attempts to open a new deal and why they failed (e.g., Can't open deal: deal is serving — the previous deal is still in progress). Handy for debugging and for understanding “what and when the bot did”.

If something goes wrong

The bot behaves oddly, a deal doesn’t close, weird errors appear in the log — write to the Telegram support bot @cryptorg_support_bot. This is the fastest channel.

To help the operator immediately understand what’s happening, include in your first message:

• Login and email of your Cryptorg account.
• Bot ID (visible in the left header, e.g., ID: 168983).
• Trading pair and deal ID, if the issue is in a specific deal.
• Recent log entries — copy 5–10 lines from the «Recent actions» block around the moment of the issue.
• Screenshots of the bot card, active deal and orders — much better than a verbal description.
• Exact time (at least hour and day) you noticed the issue.

The more detailed your first message, the faster the operator finds the cause without coming back for clarifications.