Telegram messages — reference
In short
- Messages come from the service's Telegram bot (@alphafamilia_live_bot) — about your strategies and about the server.
- The sign at the start says whether to act: 🔴 — your action is needed, 🟠 — the strategy copes by itself, ℹ️ — for your information.
- The last line of every message says what to do.
Messages come from the service's Telegram bot — @alphafamilia_live_bot (the test server has a bot of its own). Each user gets messages about their own strategies. Messages about the server (start, update, service crash, service alerts) go to everyone who has strategies. Blocked users get no messages.
Messages come in the language chosen in the app (RU or EN). Numbers are written as in that language: in English with a decimal point and a comma between thousands (77,810.70), in Russian with a decimal comma and a space (77 810,70). Sums have two decimals; a sum below a cent is "<0.01"; sums in USDT, USDC, RUB have two decimals also in "Funding needs clarification" and in the remainder of "Emergency" (the exact number is in the statement and the CSV). Prices have the precision of the pair's price step; a coin's quantity is exact; percents have at most two decimals ("8.25 %", "10 %"); counters have the thousands ("1,000 cycles"). So in every message, including "Close to liquidation", "Order stuck", "Your TP price became a loss", "Funding needs clarification", "A fill after the cycle closed" ("DCA1: 0.0125 ETH at 2,833.65 USDT") and the remainder in "Emergency".
In a message about a strategy, the second line is "strategy · pair · connection", for example anna1 · BTC/USDT · binance_main. This shows which strategy it is about.
How to read a message
The sign at the start says whether anything needs doing:
- 🔴 — your action is needed;
- 🟠 — a trouble the strategy copes with by itself;
- ⚠️ — to know and check when convenient;
- ✅ — recovered, all is fine again;
- ℹ️ — for your information (the summary, group commands, access);
- ▶️ ⏸ ⏹ — the strategy is started, paused, stopped (⏸ — only for a strategy paused before: the app has no "Pause" button).
The messages about trades keep their own signs: 🟢 — a buy, 🔵 — a sale, 🟡 — partly filled, 💰 — a cycle closed, ⏹ — a cycle interrupted. So 🟢 is always a trade, and "all is fine again" is ✅.
The last line of every message says what to do: "What to do: …" or "Nothing to do." (sometimes with an explanation: "— the strategy tries again by itself", "— the strategy waits and goes on by itself"). If a long message has to be shortened, this line stays.
The "Open the strategy" button under the messages "Emergency" (liquidation and ADL included), "Not enough funds", "Close to liquidation", "Orders left on the exchange", "A fill after the cycle closed", "The account does not agree", "Averaging paused", "A position with no take-profit order", "The strategy is not updating", "The strategy works but does not trade", "The cycle closed with a loss" and "A suspicious order of the strategy" opens this strategy's screen in the app. Under "Keys reset" (with orders of several strategies) — the "Open the app" button. The server learns the app's address when you sign in to it; right after a server restart, before the first sign-in, messages come without the button.
If Telegram is unavailable or its answer could not be read, messages are not lost: they wait in the database and go out as soon as the connection is back (retries after 10 s, 30 s, 1, 2 and 5 minutes). If a message is cancelled by an event (for example, "funds are enough" after "not enough funds"), the outdated one is not sent. The service does not send "all is well" messages.
Need your decision
| Message | When | What to do |
|---|---|---|
| 🔴 Emergency | The strategy stopped by itself: trades contradict each other, a program error, a cancel was not confirmed for 15 minutes, and so on. The message gives the reason (in words, with its detail — for example, why the exchange refused the TP — and its code), what is held, and the strategy's own orders being cancelled. If the exchange refused the TP, its reply is under the reason: "Exchange reply: |
By the reason — the message's last line; the same words are on the strategy's screen. See Emergencies and faults |
| 🔴 Orders left on the exchange | The strategy could not cancel its own orders. The "Open the strategy" button | Cancel these orders on the exchange by hand |
| 🔴 The account does not agree | The account check found a discrepancy and nobody is in an emergency: the working strategies of this asset hold no share of their own (for example, a stopped strategy's coins were sold and a new strategy has not begun its cycle yet). "Less asset on the account than counted: the strategies on BTC need 0.03 BTC, there is 0.01 BTC. Strategies of this asset: …. Nobody is in an emergency: the working strategies hold no share of their own and wait until the account agrees." One message for these figures; changed ones come again. Sent by the first of the waiting strategies, with the "Open the strategy" button. See If the account has less asset | Compare the exchange balance with each strategy's "Position" for this asset. A stopped strategy's coins sold — "Start a new cycle" or the archive for it; the asset returned to the account — the waiting strategies start by themselves |
| 🔴 A fill after the cycle closed | An order filled when the cycle was already closed. The "Open the strategy" button | Check the balance on the exchange |
| 🔴 The exchange refused the manual order | Your manual limit order did not pass the exchange's rules (price outside the band, amount below the minimum, step): "Reason: …. The order is taken off." and "Exchange reply: |
Correct the price or the amount and try again |
| 🔴 Manual N: the market buy was not made | A "Market" purchase (for "sell first" and a short — "the market sale was not made") bought nothing (not enough funds, the exchange refused, limit-only trading, not sent within 2 minutes after the command): "Reason: …. It is not repeated — the command is over.", "… needed, … free", the exchange's reply. One message. A copy gets the same with ⚠️ and "Nothing to do" | Top up the account or change the amount and buy again |
| 🔴 Close to liquidation | Futures: the mark price is within 10 % of the liquidation price; one message per cycle. The strategy does not close the position. The "Open the strategy" button | Decide whether to close the position — by hand on the exchange (the strategy then goes into an emergency and waits for your decision) |
| 🔴 Averaging paused | Futures: the pair's leverage or the account's mode was changed on the exchange (Hedge Mode and cross margin are needed). The strategy took off its orders that add to the position (the entry, the averaging levels) and places no new ones; what was filled is counted, the TP stays. One message per change and reason; a restart of the service or an update does not repeat it. The "Open the strategy" button | Set the strategy's leverage back for this pair on the exchange (or Hedge Mode and cross margin) — the strategy goes on by itself within a minute |
| ✅ Averaging resumed | The leverage and the account's mode on the exchange are as the strategy needs again: it places its orders by the plan | Nothing |
| 🔴 A position with no take-profit order | The system's guard: the strategy works, holds a position, and its take-profit (TP) order has not been on the exchange for 5 minutes — whatever the cause. A message comes for every such case (a restart of the service does not repeat a lasting one and does tell of a new case after it); with the button "Open the strategy". Not sent for a strategy on pause, stopped or in an emergency (they have their own messages), when a limit entry is filled only in part (the TP waits for the whole entry), when the TP is below the exchange's minimum or has no price (those have their own messages) and when the market is closed. The guard only tells: it closes and places nothing by itself | Open the strategy and see what it waits for. If there is no reason — "Stop", then "Start" → "Continue the cycle": the strategy checks itself against the exchange and places the order again. No help — tell the developer |
| ✅ The take-profit order is on the exchange again | The strategy's position is covered by its take-profit order again (or is closed already) | Nothing |
| 🔴 The strategy is not updating | The system's guard: the strategy is working, but its state has not been updated for 5 minutes — it neither checks itself against the exchange nor places new orders; the orders already on the exchange stay. The time counts from the last update, and after "Start", the end of a pause and "Start all" — from the moment the strategy was due to begin working. One message per case; with the button "Open the strategy" | Tell the developer. If it cannot wait — "Stop", then "Start" → "Continue the cycle" |
| ✅ The strategy is updating again | The strategy checks itself against the exchange and places orders again | Nothing |
| ⚠️ The strategy works but does not trade | The system's guard: the strategy is working, but has had no order on the exchange for 30 minutes; the message says what it waits for (for example, "the account does not agree in BTC: the strategies on BTC need 0.03 BTC, there is 0.01 BTC; the strategies of this asset: …", "the check waits for a strategy of the account to be loaded (…)", "the pair's leverage on the exchange differs from the strategy's"). One message per case, and of a lasting case once a day at most (a restart of the service on the same day does not repeat it); with the button "Open the strategy". If the entry order waits for its retry after a refusal, the reason is named also after a restart of the service: "the account lacks the funds for the order (… needed, … free)" — by the strategy's settings and the free amount the strategy already knows (no request to the exchange); if the strategy does not know the amount now, the message says so. Not sent for a strategy on pause, a closed market, a limit entry that waits for its price, a copy that waits for its lead strategy's cycle, and a strategy that stops after the cycle | Open the strategy — its screen says what it waits for and what to do. If that is as meant — nothing |
| ✅ The check after the start: all is well | For the system administrator only, ten minutes after every start of the service (after an update too): how many strategies work; every position has its take-profit order, all are checked against the exchange, no new emergencies and no program errors. If no strategy works ten minutes after the start (the vault is locked, the strategies are not started), the check waits: it comes once strategies have worked for ten minutes and says how many minutes after the start of the service it was made | Nothing |
| 🔴 The check after the start: something to look at | For the system administrator only, ten minutes after the service started: how many strategies work and what is wrong — positions with no take-profit order, strategies not through the check against the exchange, in an emergency since the start (also at the very first step; an emergency of before the start does not count), switched off by a program error; the strategies are named. It also comes when no strategy works any more after the emergency | Open the strategies named and see the reason; if it is not clear — tell the developer |
| ⚠️ Margin reserve of the account | The system's guard, for futures accounts with strategies loaded only: less than 30 % of the account's margin is not held by positions (the margin balance with the unrealized result less the positions' margin ÷ the margin balance; the margin held for the grid's resting orders is not taken off, so a full grid alone causes no message). The margin is shared by all pairs (cross): the liquidation of one position can take the whole account. The message names the connection, the share and the sums. One message per case; a case ends when the share is 35 % or more again | Add funds to the account or reduce the positions — it is your decision; the strategies close nothing by themselves |
| 🔴 Critical margin reserve of the account | The same when less than 15 % of the margin is free. One message per case; again — if the share rose to 20 % and fell below 15 % once more | The same |
| ✅ The margin reserve is back | 35 % or more of the account's margin is free again | Nothing |
| ⚠️ The cycle closed with a loss | The system's guard: a strategy's cycle completed, and its result in the profit asset is negative. The system has no stop-loss, so such a result should not be. One message per cycle; with the button "Open the strategy". Not sent when the cycle closed at your TP price with a loss you confirmed (a copy: at such a price of its lead strategy), when the cycle was interrupted, and while a fee of the cycle is still to be clarified | Look at the cycle in the strategy's history; if the reason is not clear, tell the developer |
| ⚠️ A suspicious order of the strategy | The system's guard: an order of a working strategy rests on the exchange that cannot be right. The message names the reason — one of three — and the order itself (which one, a buy or a sale, the quantity, the price, the sum). 1) An entry or grid level order is larger than the strategy's whole budget. 2) The order's price is more than 50 % away from the market price and also beyond the strategy's own grid and TP (a deep level of a correct grid and the TP after a deep drawdown are not such). 3) The take-profit order is larger than the strategy's position; on spot "sell first" — the buy-back costs more than the cycle's sales brought. The guard does not touch the order: it stays on the exchange, the strategy goes on working. One message per order, if it stays so for half a minute; with the button "Open the strategy". Not checked: the amount of your manual averaging (you set it; over the budget only with your confirmation) and the price of your TP ("Move the TP"); the price of a manual averaging is checked — it is told once. No fresh market price — the rule about the price is silent | Look at the order in the strategy's "Levels" and on the exchange; if it is not your manual one, stop the strategy and tell the developer. A copy: look at the order on the strategy's screen ("Strategy's orders") and on the exchange; if it is not the lead strategy's manual order, stop the strategy and tell the developer |
| 🔴 Keys reset | You clicked "I forgot the password": the vault's keys are removed, the strategies stopped, their orders stayed on the exchange. The message lists those orders (strategy, pair, order, side, quantity, price); a long list shows only whole lines and "and N more" at the end. The "Open the app" button | "What to do: set a new vault password in the Profile ("Vault settings"), then "Replace key" on the connections and press Start: "continue" keeps the orders, "new cycle" takes them off." |
| 🔴 Service started | After a reboot of the server, and after a restart of the program if your vault was locked: the key vault is locked, the strategies do not trade, the orders on the exchange are untouched. The version is given | Open the key vault in the app and start the strategies |
| ✅ Service started, the strategies work | The system administrator alone (owner's decision 19.11): after a restart of the program (an update, a rollback, a fault) the vaults opened by themselves, "The strategies go on: N" — of every user together. A user whose vault was open gets nothing. Stopped strategies and strategies in emergency do not start by themselves | Nothing |
| 🔴 The strategies wait for you | Strategies should be trading but are not: the vault is locked, or "Start" was not clicked after a restart. Every hour while this lasts | Open the key vault and start the strategies in the app |
| 🔴 Binance banned the server's address | The title names the exchange that banned the address: Binance, BingX or Bybit. The exchange banned requests from the server's address (code 418). All the server's Binance strategies of the API that is banned (spot, USD-M or COIN-M) wait — not only the strategies of one key. The wait is exactly the time the exchange gave, at least 2 minutes; if no time was given — 2 minutes, twice as long for repeated bans in a row, up to 3 days. There are no test requests before the time is up — they would lengthen the ban. Orders on the exchange stay and may fill. A message about each new ban goes to every user who has connections there. This should not happen — the developer looks for the cause. On Bybit the answer "server is busy" (403 Server is busy) is not a ban: requests to Bybit wait one minute with no message and go on; the message about a ten-minute ban comes only if the refusal repeats within the next 5 minutes | Tell the developer; the strategies go on by themselves when the time is over |
| 🔴 Two servers manage one account | Strategies of two servers of the system (the main and the test one, say) run on the same exchange account. The strategies start as usual, but each server takes the other's orders for unknown ones and stops its own strategies in an emergency. Comes once a day while it lasts; names the connections and the other server's address | Keep the strategies of this account on one server — stop them on the other |
| 🔴 The server's clock is not kept in time | To the system administrator, at once (two checks in a row, two minutes apart): the exchanges' prices look stale, the strategies place no new orders and may report a "Technical fault"; the orders placed stay | On the server: timedatectl set-ntp true, check with timedatectl; if that does not help, tell the developer |
| ✅ The server's clock is kept in time again | To the system administrator, once after the message about the clock | Nothing: the strategies go on by themselves |
| 🔴 The server's disk is almost full | To the system administrator, at once, when 95 % or more is used (checked every two minutes). When the room runs out, the database stops writing and the strategies cannot trade; the orders placed stay on the exchange. The morning summary marks the disk from 80 % | On the server: df -h /, remove old copies of the database and logs; if that does not work, tell the developer |
| ✅ The server's disk has enough room again | Less than 90 % is used | Nothing |
| 🔴 The guard "…" does not work | To the system administrator: one of the system's checks (for example, "a position without a take-profit order") ended in a program error three passes in a row — while so, this guard tells nothing; the strategies trade as usual and the other checks go on. Once until the service is restarted; the message names the check and the error | Tell the developer; until it is fixed, check what this guard watched yourself |
Warnings (the strategy goes on by itself)
| Message | When | What to do |
|---|---|---|
| 🟠 Not enough funds | No money for the entry or an averaging order: how much is needed, how much is free and how much is missing. If part of the free amount is other strategies' coins on this account (their share, or what their orders may have just bought), it is told apart: "Of it, … belongs to other strategies of this account"; the missing sum is counted without it. Retry after 5, 15, 30, 60 minutes, then once an hour. The TP stays. If the exchange refused — its reply: "Exchange reply: |
Top up the account by the missing sum or lower the strategy's budget in "Change settings" (from the next cycle). A manual limit order ("Manual N"): top up the account or cancel the order in "Levels" ("Manual orders" → "Cancel") — the budget does not change it |
| ✅ Funds are enough | The order that was short of funds is placed | Nothing |
| ✅ Manual N — the order is on the exchange | Your manual limit order is placed: "A limit buy of … at …". If it was short of funds before, this message replaces "Funds are enough" | Nothing |
| ✅ Order placed | The order the exchange refused for another reason (its rules and so on) is placed: "… placed after the exchange's refusal" | Nothing |
| 🟠 The exchange refused an order | With the reason in words ("the order breaks the exchange's rules…", "another reason given by the exchange"), the retry time and the exchange's reply as it came: "Exchange reply: 101211 The order price is out of range" (up to 200 characters; keys and signatures hidden). The same reply is in the strategy's "Events" | Nothing — the strategy tries again by itself |
| 🟠 Technical fault | 5 minutes without a working step (no connection, no quote, unknown fee). A reminder every 30 minutes. A closed T-Invest exchange at night and at weekends is not a fault. When the reason is "the exchange does not take the connection's key", the message's sign is 🔴 | Nothing — the strategy waits and goes on by itself. The key is not taken — check the key on the exchange and replace it in the connection |
| ✅ Recovered | One message after a fault | Nothing |
| 🟠 Binance halted trading of the pair | For BingX strategies — "BingX halted trading of the pair", for Coinbase strategies — "Coinbase halted trading of the pair"; at Coinbase it also comes when the pair takes limit orders only and a market entry has waited 15 minutes (Coinbase). The strategy saw trading of the pair halted 15 minutes ago (Binance: the strategy sees a halt at once when an order is refused, otherwise within 5 minutes). This is not an emergency: the strategy waits and tries again, orders on the exchange stay. A closed T-Invest session (night, weekend) is the normal schedule and is not reported | Nothing — the strategy waits and goes on by itself |
| 🟠 The entry is only partly filled, no TP is set | The limit entry filled partly and has not grown for 15 minutes. The strategy waits for the whole entry and only then places the TP; the part bought stands without a TP for now, the entry is moved toward the market. One message a cycle | Nothing — the strategy waits and goes on by itself |
| ✅ Trading of the pair is back | One message when trading is back (on Binance the strategy sees it within 5 minutes) | Nothing |
| ⚠️ Comparison with the exchange: differences | Every night the system itself compares the results of the closed cycles with the exchange's data. For the connection named, the result the strategy recorded does not match the exchange: how many cycles of how many. Comes right after the comparison — to the connection's owner and the system administrator. The strategies work as usual | Tell the developer — these cycles will be looked into |
| 🟠 The comparison with the exchange was not made | The night's comparison of a connection did not pass: it was not done in 2 hours, did not start, gave no result — or did not read the exchange's trades to the end (how many cycles were not compared). The next night takes the same period. Comes to the connection's owner and the system administrator | If the message comes again, tell the developer |
| ⚠️ Funding needs clarification | Futures: a funding payment came for a time the strategy has no record of its position for (a restart). Not booked | Check the payment against the Binance statement |
| 🟠 Funding is not read | Futures: the exchange has not given the funding payments for 30 minutes (for example, the request limit is busy) while the strategy holds a position. Trading goes on, the TP stays. The payments of that time are booked in their cycles once the exchange answers — until then the cycles' profit is without them. One message | Nothing |
| ✅ Funding is read again | One message after "Funding is not read": the payments of that time are booked in their cycles, closed ones included | Nothing |
| ⚠️ Your TP price became a loss | Your TP (in percent or at a price) would close the cycle at a loss that was not agreed: the exchange's fee rose or the position changed (a DCA after a consent to a loss — the consent holds for the position it was given for). "Price …: with the venue's current fee and position the cycle would close at a loss…". The strategy's TP is back | If you need your own TP — set it again on the "TP" screen and confirm the loss; otherwise nothing |
| 🟠 Strategy's order removed by someone else | A strategy's order was cancelled or changed by hand (in the exchange's or broker's app). What was filled is counted; the strategy places the order again by its plan. Your order is yours: the strategy does not touch it | Nothing |
| ⚠️ Order stuck | The price passed the order's level 10 minutes ago, no fill | Check the order on the exchange — the strategy waits for its fill |
| 🔴 No TP placed: the fees and the funding ate the profit | COIN-M only: the cycle's fees and funding in BTC are more than any price can give with the set TP profit (an inverse contract's profit in BTC has a ceiling) — there is no TP price, no TP is placed. "Position 45 contracts: the cycle's fees and funding in BTC are more than any price can give with the set TP profit of 1 %…". The DCA levels stay. One message per cycle and position (after a level fills — again, if there is still no price); the reason is on the strategy's screen too | Lower the TP % in the strategy's settings or set your own TP with the "TP" button (by price — at a loss too, if you agree); otherwise the strategy waits without a TP |
| ⚠️ DCA level skipped | The grid levels are counted from the actual entry price. If the entry filled worse than the price the grid was checked at before the cycle started (higher for a buy, lower for a sell; for example, slippage of a market entry), a level may come out below the exchange's minimum — the exchange would not take such an order. The strategy skips this level and places the next one; the TP works as usual. The skipped level is not placed until the cycle ends, even if the exchange lowers its minimum; a new cycle counts its levels afresh. A DCA order already on the exchange is not cancelled, even if the exchange raises its minimum: only a level not placed yet is skipped. The message names the level, its size and the exchange's rule with its number, for example "DCA1 — 0.00009 BTC ≈ 4.51 USDT: below the exchange's smallest quantity 0.0001 BTC ≈ 5.01 USDT". When the level's sum is very close to the minimum, it is rounded down and the minimum up, so that the level is seen to be smaller: "≈ 4.99 USDT: below the exchange minimum 5.00 USDT". One message per level and cycle; the same in the strategy's "Events" | Nothing |
| ℹ️ Averaging levels cancelled | You took levels off the rest of the cycle: "DCA 3–5 — the strategy buys no more at them until the cycle ends; the TP stays". The current cycle only; the next one has the whole ladder | Nothing |
| ℹ️ Level restored / Levels restored | The levels taken off are back in the ladder: the strategy places them in turn | Nothing |
| 🟠 Cancel not confirmed | 5 minutes without confirmation; after 15 minutes — an emergency | Nothing — the strategy waits and goes on by itself |
| 🟠 Trades are late | The exchange shows a fill, but there have been no trades for 5 minutes | Nothing — the strategy waits and goes on by itself |
| 🟠 The Binance event stream is not working | For BingX connections — "The BingX event stream…". The Binance account event stream of a connection (on it the exchange tells of fills at once) has not worked for 10 minutes in a row. The strategies trade as before — they learn of fills by asking the exchange, a TP may come a few seconds later, no fill is lost. One message | Nothing |
| ✅ The Binance event stream works again | One message after "The Binance event stream is not working", with how long it was down: the strategies learn of fills at once again | Nothing |
| 🟠 High load on the server's address at Binance | For the system administrator only. The requests from the server's address took 70 % of Binance's limit of a minute on spot (6000) or 85 % on futures (2400; COIN-M futures have their own limit of 2400 and the same thresholds, the message says "COIN-M futures: …") — by our count or by the exchange's own, if it is larger (so another program on the same address shows too). Above the strategies' own share (spot — 50 % of the limit, futures — 80 %) the strategies' ordinary requests wait, while take-profits and cancels go on — up to 95 % of the limit. One message — the next when the load falls; a restart of the service does not repeat it. For the testnet — the same message marked "(testnet)" | Nothing; if this message comes often, tell the developer |
| ✅ The load on the server's address at Binance is normal | One message after "High load…": the load has been at most half of the limit for 5 minutes in a row. The strategies themselves take at most half of the limit on spot and at most 80 % on futures, so "High load" is a sign of another program on the server's address or of urgent TPs beyond the strategies' share | Nothing |
For your information
The last line of the messages about trades is "Nothing to do." unless said otherwise.
With many trades (dozens of strategies, short cycles) the messages about trades and cycles come in batches: the first at once, the rest of the same minute as one message "📦 Trade messages: N" — the same messages inside, in order, each under a line with its number "━━━━━━━ 2 of 3 ━━━━━━━"; if they do not all fit into one Telegram message, the last line is "… and N more — the details are in the application" (every trade is on the strategy's screen). So one chat gets at most one message about trades a minute — otherwise Telegram stops taking the bot's messages for a while altogether, the alerts included (as on 15.11: four hours without a single message). Alerts, warnings and every other message never wait for a batch.
| Message | When | Can be turned off |
|---|---|---|
| 🟢 🔵 Buy / sell filled: entry / DCA1 of N / Manual N | An entry, averaging or manual order filled (🔵 — a sale: "sell first" and a futures short). The message: "Bought" ("Sold"), "Price" and "Spent: 35.92 of 40.00 USDT" — the cycle's trades at their prices, before fees (as the grid is sized), out of the cycle's budget; manual orders beyond the grid can take it past the budget (spot "sell first": the coin sold out of the budget in it: "0.045 of 0.1 ETH"); the "Position" block — "Quantity" and "Cost" with the fees in, "Average price" — by the prices of the trades, without fees, and "Break-even" — the price with the fees ("sell first": "To buy back", "Proceeds", "Average sale price", "Break-even"); "Planned TP" — the TP price the strategy works with after this trade. 🟡 "…partly filled" — not all of the order is filled: "Order filled: 0.01 of 0.02"; if it is the entry, instead of the TP price — "TP — once the entry is filled in full". Several trades of one order that came together — one message. Futures: "Position long ×3" (or short), "Margin", "Funding of the cycle". COIN-M: instead of "Spent" — the trade's "Notional" in the coin and in USD, before fees; so does a partial TP fill (the trade's "Notional" / "Sum"). T-Invest: the quantity also in lots — "20 SBER (2 lots)" | Yes, the switch in the "Notifications" card on the strategy's screen; a manual order ("Manual N") — always |
| 💰 Cycle N closed | The TP filled: "Take-profit filled" — "Sold" ("sell first": "Bought back"), the price and the sum before fees (futures: "Notional"); "Profit of the cycle", "Last 30 days", "All time"; "Duration", "Buys in the cycle" ("Sales in the cycle"), "Cycles closed: N in 30 days · M in all" (closed by the TP). Futures: also "Leverage" and "Funding of the cycle (in the profit)". COIN-M: the quantity in contracts, the profit and the funding in BTC (8 places), the line "In USD at the close price". If the cycle leaves a remainder below the minimum order — the line "The remainder … (≈ …) is below the minimum order — carried to the next cycle."; on futures — "A position of … stays on the exchange — carried to the next one.", and if the strategy is stopped after this cycle — also "⚠️ The strategy is stopped: this position is on the exchange without orders." (then close it on the exchange yourself or start the strategy). If the broker's fee has not come yet — "Needs clarification". There is no separate message about the TP fill | Yes, the same switch |
| ⏹ Cycle N interrupted | The cycle was closed by your command "Start a new cycle" or when the strategy went to the archive: the profit of the filled part of the TP (if any), what is left — "Left: … — yours: the strategy does not sell it and does not carry it into the new cycle" ("sell first": "Not bought back …"; futures: the open part of the position stays on the exchange and is yours now), the duration and the number of buys. The last line: "What to do: the remainder is yours — deal with it on the exchange yourself if needed." (futures — "close that part of the position on the exchange yourself if you do not need it"); with nothing left — "Nothing to do." | Yes, the same switch |
| ▶️ ⏸ ⏹ Strategy started / paused / stopped | A command to one strategy. The second line says what it means: "The strategy trades by its plan.", "Orders stay on the exchange, no new ones.", "Own orders are cancelled, nothing is sold." | No |
| ℹ️ Start / Stop: N | A group command — one message with the list of strategies instead of a separate one for each; a long list shows only whole names and "and N more" at the end | No |
| ℹ️ Alphafamilia Algo summary | Every morning at 09:00 Madrid time: how many strategies are working, waiting for the vault or a start, in an emergency, paused or stopped, how many cycles are open; "The open cycles' result if closed now" — at the last price of the loaded strategies (for the others — "Without a price: N — the vault is locked or the strategy not started"; if no strategy has a price — "The open cycles' result: no price — the vault is locked or the strategies not started"; for strategies in an emergency without a price — "In an emergency: N — no result counted", and if there are no other open cycles — "The open cycles' result is not counted: N in an emergency"; if an emergency strategy's price is known, its result is counted with the rest); "Profit of the last 24 h" — of the cycles closed in the last 24 hours, per currency (the BTC of COIN-M strategies — a line of its own with USD for reference: "+0.00047679 BTC (≈ 45.47 USD)") ("Needs clarification" if the broker's fee has not come yet); "🔴 In an emergency:" and the names of the strategies in an emergency — whole names only; if there are more than 20 strategies or the names do not fit, "(+N)" after them says how many more. For the system administrator also — the version, whether the database answers, when the last nightly (full) database copy was made (⚠️ if more than 26 hours ago or there is no information), how full the disk is (⚠️ from 80 %), the highest load on Binance over 24 hours — the share of the server address's limit of a minute on spot, futures and, if there are COIN-M connections, "COIN-M futures" (⚠️ from 70 % on spot and from 85 % on futures), a warning if the copies go to the Mac unencrypted, and if the server's clock is not kept in time. The last line — what to do today: open the vault and start the strategies, sort out the emergencies, turn the copies' encryption on, tell the developer of the ⚠️ — or "Nothing to do." Sprint 46: the line "Compared with the exchange" — the result of the night's comparison of the results with the exchange for your connections: "N cycles, no differences" (and "Not compared: N" when the exchange has no data for some cycles), "⚠️ N differences in M cycles", "⚠️ was not made" or "not yet (the vault is locked or the comparison is running)"; "Connections not compared: N" — when not all were compared | No |
| ℹ️ The server over the hour | To the system administrator only — every full hour, from each server (dev and the main one write each from its own bot to its own chat), always, even when all is well. The second line — the server's site (when the service already knows it from a sign-in to the app) and the time span, Madrid time: "12:00–13:00"; the first hour after the service restarted — from its start ("12:20–13:00"), and if the service started less than 10 minutes before the hour began, that hour has no message. "Highest load on the exchanges' APIs (share of the limit of a minute)" — for each exchange the server uses, a testnet on a line of its own: Binance — spot, futures and COIN-M futures (the weight of the requests from the server's address, ⚠️ from 70 % on spot and from 85 % on futures — as in the summary); BingX and Bybit — the highest of the shares: the account's limit of each kind of request (the exchange counts them a second, here — over the minute) and the server address's limit (BingX — the market data, 500 requests in 10 s; Bybit — 600 requests in 5 s), ⚠️ from 70 %. Only this server's requests are counted: on a shared demo account the other server's requests are not in it. "Disk" — used and free (⚠️ from 80 % used, as in the summary). "Processor" — the average load of all cores over the hour (⚠️ from 80 %). "Memory" — free now, in GB and as a share of the whole (⚠️ below 10 %). The last line — the other server, as its watchdog sees it: "The server … answers", "The server … has not answered since 12:41" (⚠️ — after 5 minutes, once the watchdog has sent "not answering"), "⚠️ The server …: not known — the other server's watchdog does not run"; no neighbour set — no such line. What the service could not learn — "not known". With a ⚠️ — the sign ⚠️ and "What to do: tell the developer of the ⚠️ in this message.", without — "Nothing to do." | No |
Copying trades
These messages go to the owner of a copy (Copying trades). In the second line a copy has the mark "(copy)" after the strategy's name; its messages about trades and closed cycles are marked the same way.
| Message | When | What to do |
|---|---|---|
| ℹ️ The copy began its first cycle | "The lead strategy began a new cycle — the copy entered at its own exchange's price." | Nothing |
| ℹ️ The lead strategy averaged by hand — the copy too | The lead strategy's manual averaging turned into percent: "A step at … % from your average, … % of the balance: … at …" (by the market — "A step by the market, as the lead strategy's, … % of the balance: …") | Nothing |
| ℹ️ The lead strategy moved the TP — the copy too | "The TP of this cycle is … % net, after fees: …"; if the lead strategy took the strategy's TP back — "The TP follows the strategy's rules again." | Nothing |
| ℹ️ The lead strategy cancelled levels — the copy too | "DCA 3–5: the copy buys no more at them until the cycle ends; the TP stays"; levels the copy cannot take off (bought already, none such) are passed over with a note | Nothing |
| ⚠️ The lead strategy closes the cycle at a loss — the copy too | The lead strategy confirmed a TP worse than break-even; the copy puts its TP at the same net percent over its own cost: "TP … (… % net, after fees). The lead strategy agreed to the loss." | Nothing |
| ℹ️ The copy waits for the lead strategy | A copy without a cycle begins no new one: the lead strategy stops after its cycle. One message for the whole wait | Nothing |
| ℹ️ The lead strategy restored levels — the copy too | "DCA 4 back in the copy's ladder — it places it in its turn" | Nothing |
| ⚠️ The lead strategy's command was not applied | The lead strategy's manual command skipped, with the reason: "The copy has no open position.", "The copy is already closing its cycle by the TP.", "The copy's previous manual order is still there.", "The step's amount for the copy is below its exchange's minimum.", "No current price of the copy's exchange.", "The copy has no manual order to take off.", "The copy's exchange would not take such an order." — and "The copy goes on with its cycle." | Nothing |
| ⚠️ The lead strategy's TP is a loss for the copy | The lead strategy moved the TP at a profit for himself, but with your exchange's fee (a higher one) the copy's cycle would close at a loss: "the TP stays by the strategy. The copy's price: …" The message "The lead strategy moved the TP — the copy too" is not sent then. | Nothing |
| ⚠️ The lead strategy's TP price is a loss for the copy | The lead strategy's TP was already in force for the copy, but your exchange's fee rose, and with it the copy's cycle would close at a loss: "The copy took the strategy's TP back." | Nothing |
| ℹ️ The lead strategy's rules changed | "The copy ends its cycle by the old rules; the new ones apply from its next cycle." | Nothing |
| 🔴 The copy's balance is below the minimum | At a cycle's start: "The lead strategy's rules need at least … (every order 20 % above the exchange's minimum); the copy has …. No new cycle started." | Raise the copy's balance with "Change balance" — the copy starts its cycle by itself |
| 🟠 The lead strategy stops after its cycle | "The copy stops after its own cycle too. Its orders stay on the exchange." | Nothing — or stop the copy yourself |
| 🟠 The lead strategy stopped | The lead strategy is stopped, in an emergency, deleted or hid himself: "The copy ends its cycle and stops. Its orders stay on the exchange." (if the copy has no cycle — "The copy is stopped: no new cycles."). Once | Nothing — or stop the copy yourself |
| ✅ The lead strategy is back | The lead strategy works again before the copy's cycle ends: "The copy goes on trading by the lead strategy's rules." | Nothing |
Keys and exchange accounts
Messages about a connection's key — by the key's term (Bybit: a key without an IP list works 90 days) and by the daily check of the keys of all exchanges (The key's term and daily check), and about what the strategy switched on a Bybit futures account itself (Bybit).
| Message | When | What to do |
|---|---|---|
| ⚠️ The key of connection … expires in N d — date | 7 days before the term ends: "… will refuse the key then — the connection's strategies will not be able to trade. One more reminder on the day." | Create a new key on the exchange and replace it in the app — "Replace key" on the connection ("Profile" → "Settings" → "Exchange connections"), with the connection's strategies stopped |
| 🔴 The key of connection … expires today — date | On the last day of the term | The same |
| ⚠️ A new term of the key of connection …: until … (N d) | The daily check: the exchange told another term | Nothing now — a reminder to replace the key comes 7 days before the end |
| ⚠️ The key of connection … now has a term: until … (N d) | The daily check: a key without a term got one (e.g. a Bybit key's IP list was removed) | The same |
| ℹ️ The key of connection … has no term any more | The daily check: the term is gone — no more reminders | Nothing |
| 🔴 The key of connection … no longer works | The daily check: the key is not accepted — deleted, expired or changed. The connection's strategies cannot trade | Check the key on the exchange; if it is gone or has expired, create a new one and replace it in the app ("Replace key", the connection's strategies stopped) |
| 🔴 Exchange key (…): withdrawals are on | The daily check: such a key can take money off the account; the strategies go on trading | Switch withdrawals off in the key's settings on the exchange |
| 🔴 Key check: a key may withdraw funds | Once a day, from 09:00 (Madrid), one message about all your connections — by what the last daily check of the keys found: the connections whose key may withdraw funds and the connections whose key is not bound to an IP address are named. Practice accounts (testnet, VST, demo, sandbox) are left out of the message. It comes every day while this lasts; the strategies go on trading. What the exchange does not tell about a key is not mentioned | In the key's settings on the exchange switch withdrawals off and allow access from the server's IP address only. The message stops after the key's next daily check |
| ⚠️ Key check: a key is not bound to an IP address | The same when no key may withdraw, but some keys are not bound to an IP address | In the key's settings on the exchange allow access from the server's IP address only |
| ⚠️ Exchange key (…): no trading permission | The daily check: the connection's strategies cannot place orders | Switch trading on in the key's settings (for futures — the futures permission) or replace the key |
| ⚠️ Bybit (…): the account's USDT futures switched to hedge mode | The strategy switched it itself: the strategies need hedge mode, and nothing was open in the account's USDT futures. This changes the mode for manual trading too | Nothing; if you trade on this account by hand, mind the new mode |
| ⚠️ Bybit (…): the futures limit order price protection switched to "reject" | The strategy switched it itself: an order priced outside the allowed limits is now rejected, not moved. It applies to all the account's futures | The same |
| ⚠️ Binance (…): little BNB left for fees | The daily key check: paying fees in BNB is on at the exchange, and the free BNB beyond what the strategies count is below 0.02 BNB or below 12 USDT at BNB's price. When it runs out, the exchange takes the fee from the coin received. If the account's strategies count BNB too, a line says that is not a reserve. Once a day per connection; nothing stops | Top up BNB on the spot account or turn paying fees in BNB off |
| ⚠️ Binance (…): little BNB left for futures fees | The same for the futures wallet: the BNB fee discount is on, and the BNB on the wallet is below 0.02 BNB or 12 USDT. When the BNB is not enough, the fees go without the discount | Move BNB to the futures wallet or turn the discount off |
| ⚠️ BingX (…): a trade not counted for any strategy | The exchange never named the trade's order, and it is none of the strategies' orders: this happens with a liquidation, auto-deleveraging (ADL) or your manual order. The strategies do not count this trade | Check whose trade it is; if it is a strategy's, the position check notices it |
| ⚠️ BingX (…): the exchange does not show some trades | The exchange has not given the trades of some second for 10 minutes — the strategies read on without them. If a strategy's order filled in that second, the check of the position and the asset notices it | Nothing; if an "Emergency" comes — see its "What to do" line |
Registration
| Message | To whom and when | What to do |
|---|---|---|
| 🔴 Request to register | To the system administrator, when registration is "Open, with approval" and a new person opened the app in Telegram or signed in in a browser with "Sign in". The name from Telegram and the Telegram ID are given. Under the message — the buttons "✅ Approve" and "❌ Reject" | Approve or reject the request — with a button under the message ("Administration" opens at this request, and the decision is to be confirmed) or in the app: Profile → Administration. Without buttons — in the app only |
| ℹ️ Access granted | To the person whose request was approved | Open the app with the bot's button in this chat |
Service alerts
"Service alert" goes to everyone who has strategies (about a specific strategy — only to its owner) when the trouble is not in trading but in the service itself. Its sign is by the cause:
| Text | Sign | What it means and what to do |
|---|---|---|
| "The database does not answer: no new orders, the placed ones stay. The strategy goes on by itself when the database answers." | 🟠 | The database has been unavailable for 5 minutes. Nothing to do |
| "The database answers again." | ✅ | The database is back. Nothing to do |
| "Program error: emergency of this strategy, its orders are cancelled, the other strategies work." | 🔴 | An error in the program of one strategy. "Emergency" comes too — see its "What to do" line. If the database did not answer at that time, the emergency is not recorded: the strategy is switched off, its orders are taken off, and after a restart of the service it stays stopped until you press its "Start" |
| "Orders could not be cancelled" | 🔴 | Check the strategy's orders on the exchange and cancel them by hand |
| "The strategy could not be prepared" | 🔴 | The strategy did not load. Tell the system administrator |
| One exchange account under two connections | 🔴 | Two connections made before the present rules trade one market of the account (or one of them is mixed, with spot and futures). Spot and futures of one account under two connections are normal and give no signal. Tell the system administrator |
| An error in the service's loop | 🔴 | Tell the system administrator |
| Another cause | ⚠️ | Tell the system administrator |
Server messages
If the service crashed or hung (2 minutes without signs of life), the server itself sends the system administrator "the service crashed" and restarts it; a user whose vault was open gets nothing (the strategies go on by themselves), one whose vault is locked gets "Service started" (the vault password is needed).
The server also reports on its own jobs, without the service. The messages in this table go to the system administrators alone (owner's decision 19.11: a user gets only what asks for something), only in Russian, with their own signs and without the "What to do" line; the English words here are a translation.
| Message | When | What to do |
|---|---|---|
| 🔴 The Alphafamilia Algo service crashed | The service crashed and is restarting | Wait for "✅ Service started, the strategies work"; the users with a locked vault get "🔴 Service started" from the service itself |
| 🔴 The Alphafamilia Algo service crashed and stopped | Too many crashes in a row; there will be no restart. Orders on the exchange stay | Look into it: journalctl -u vnext2 |
| 🛠 Alphafamilia Algo update | A new version is being installed. The strategies stop for a few minutes; orders on the exchange stay. The message says whether the strategies go on by themselves or the users will have to open the vault | Wait for "Service started" |
| 🟠 Alphafamilia Algo: the nightly database copy was not made | The daily copy failed | The strategies keep trading; tell the developer |
| 🟠 Alphafamilia Algo: the hourly database copy was not made | The hourly copy of the database failed | The same |
| 🟠 Alphafamilia Algo: the weekly check of restoring from a copy failed | The weekly check that a copy can be restored failed | The same |
| 🟠 Alphafamilia Algo: the quarterly log archive was not built | The quarterly archive of the server's logs was not built | The same |
| 🔴 Update to … failed | The new version did not pass the check or did not install. If the service was stopped meanwhile, the previous version was put back (and, if needed, the database from a copy) — then the message says "open the key vault" | Open the vault and start the strategies, if the message says so |
| 🔴 Update to … failed, and the rollback failed | The service is not running. Orders on the exchange stay | Tell the system administrator |
Where to see the details
- Command journal ("Profile" → "Command journal"): who gave which command and when, and how it ended.
- Events on the strategy's screen: what the strategy did and why.
- Download diagnostics (no secrets) (at the bottom of the strategy's screen): one file with the strategy's state, orders and latest events, without keys or passwords. You can send it to the developer.
Next: Alphafamilia Algo Help