Alphafamilia Algo Help

A Telegram message came

At the end of this path one look at a message tells you whether anything needs doing, and you know what. Here — how to read the messages and what to do for each sign; the exact texts of all messages are in the messages reference, the walk-through by what you see on the strategy's screen — in Something went wrong. An unfamiliar word — in the glossary.

What you need

  • Telegram with the chat of the service's bot @alphafamilia_live_bot — the messages come there.
  • The app: most actions are done on the strategy's screen.

Messages come in the app's language (RU or EN). The server's messages about an update, a service crash and the nightly copy come in Russian only.

Steps

  1. Look at the sign at the start. It says whether to act: 🔴 — your action is needed; 🟠 — a trouble the strategy copes with by itself; ⚠️ — to know and check when convenient; ✅ — all is fine again; ℹ️ — for your information. What each means — below, in The signs.
  2. Read the second line — which strategy it is about: “strategy · pair · connection”, for example anna1 · BTC/USDT · binance_main. A copy has “(copy)” after its name.
  3. Read the last line — what to do: “What to do: …” or “Nothing to do.”. Every message of the service has it, and it stays even when a long message is shortened.
  4. Press “Open the strategy” if the button is there (under “Emergency”, “Not enough funds”, “Close to liquidation”, “Orders left on the exchange”, “A fill after the cycle closed”, “The account does not agree”, “Averaging paused” and the guards' messages about a strategy — the full list is in the reference) — this strategy's screen opens. Under “Keys reset” — “Open the app”.
  5. Do what it says, and wait for the message with the ✅ sign where one is due (“Funds are enough”, “Order placed”, “Recovered”).
  6. Not clear — find the message by its title in the reference, or open the strategy and sort out what you see on its screen with Something went wrong.

The signs: what they mean and what to do

🔴 — your action is needed

The strategy will not fix it by itself. Do what the last line says.

Message What to do In detail
🔴 Emergency The strategy stopped by itself, cancelled its orders, sold nothing. Do what “What to do” says, then “Continue the cycle” or “Start a new cycle” Emergency
🔴 The account does not agree The account has less asset than the strategies counted, and nobody is in an emergency (usually a stopped strategy's coins were sold). Compare the balance on the exchange with the “Position” of every strategy of this asset; a stopped strategy's coins sold — “Start a new cycle” or the archive for it; the asset brought back — the waiting strategies begin by themselves If the account has less asset
🔴 A position with no take-profit order A working strategy with a position has had no TP on the exchange for 5 minutes. Open the strategy and see what it waits for; no reason — “Stop”, then “Start” → “Continue the cycle” Reference
🔴 The strategy is not updating The strategy works, but for 5 minutes it has not checked itself against the exchange nor placed orders. Tell the developer; cannot wait — “Stop”, then “Start” → “Continue the cycle” Reference
🔴 Critical margin reserve of the account Futures: less than 15 % of the margin is free. Top up the account or reduce the positions — the strategies close nothing by themselves Reference
🔴 No TP placed: the fees and the funding ate the profit COIN-M only: there is no TP price. Lower the TP % or set your own TP with the “TP” button Reference
🔴 Service started, 🔴 The strategies wait for you The server restarted: open the vault and start the strategies The vault is locked after a restart, Server restart
✅ Service started, the strategies work The system administrator alone: the program restarted, the vaults opened by themselves, the strategies go on. A user gets nothing — there is nothing to do Server restart
🔴 Orders left on the exchange The strategy could not cancel its orders — cancel them on the exchange by hand Warnings about orders
🔴 A fill after the cycle closed An order filled when the cycle was already closed — check the balance on the exchange Reference
🔴 Close to liquidation Futures: decide whether to close the position. The strategy does not close it Futures, Liquidation
🔴 Averaging paused Futures: the leverage or the account's mode was changed on the exchange, the strategy took its averaging levels off. Set the strategy's leverage (or Hedge Mode and cross margin) back — the strategy goes on by itself Futures
🔴 Keys reset You pressed “I forgot the password”: set a new vault password, “Replace key” on the connections, then “Start” I forgot the password
🔴 The key of connection … expires today, 🔴 … no longer works Make a new key on the exchange and replace it: “Profile” → “Settings” → “Exchange connections” → “Replace key” (the connection's strategies stopped) Replace the key, A second exchange, a new key
🔴 … key (…): withdrawals are on Turn withdrawals off in the key's settings on the exchange Security
🔴 Key check: a key may withdraw funds Once a day, about all connections. Turn withdrawals off in the key's settings and allow access only from the server's IP address Reference
🔴 The exchange refused the manual order Your manual order broke the exchange's rules (the price, the minimum amount, the step) and is taken off already. Correct the price or the amount and buy again (“Average”) The exchange refused an order
🔴 Manual N: the market buy was not made Nothing was bought, it is not retried. Top up the account or change the amount and buy again Not enough money
🔴 The copy's balance is below the minimum Raise the copy's balance: “Change balance” — the copy begins its cycle by itself Change a copy's balance
🔴 Binance banned the server's address Tell the developer; the strategies go on by themselves when the term ends Reference
🔴 Two servers manage one account Keep the strategies of this account on one server — stop them on the other Reference
🔴 Service alert A fault of the service itself: read the text; “The strategy could not be prepared…” and the like — tell the system administrator Service alerts
🔴 The check after the start: something to look at, 🔴 The server's clock is not kept in time, 🔴 The server's disk is almost full, 🔴 The guard “…” does not work To the system administrator only: what to do is in the reference, in this message's row Reference
🔴 Request to register To the system administrator only: approve or reject it with the button under the message Registration

🟠 — the strategy copes by itself

Usually nothing is to be done: the strategy waits or retries by itself, the orders on the exchange are untouched. When all is well again, a message with the ✅ sign comes. An action may be needed only here:

Message What to do In detail
🟠 Not enough funds Top up the account by the missing amount from the message — or nothing, if money is about to be freed. The strategy retries in 5, 15, 30, 60 minutes, then once an hour Not enough money
🟠 The exchange refused an order Nothing. If it repeats for long — read the reason and the “Exchange reply” line in the message or on the strategy's screen The exchange refused an order
🟠 Technical fault Nothing. Longer than an hour — check whether the exchange works Technical fault
🟠 The lead strategy stops after its cycle, 🟠 The lead strategy stopped Nothing — the copy finishes its cycle and stops; or stop it yourself. Then choose another trader A copy waits

The other 🟠 — “Strategy's order removed by someone else”, “Cancel not confirmed”, “Trades are late”, “… halted trading of the pair”, “Funding is not read”, “The … event stream is not working”, “The database does not answer” — need nothing from you. What each means — in the reference.

⚠️ — to know and check when convenient

The strategy goes on. Check when you have time:

Message What to do
⚠️ Comparison with the exchange: differences Tell the developer — these cycles will be looked into; the strategies work as usual
🟠 The comparison with the exchange was not made If the message comes again, tell the developer
⚠️ Order stuck Check that order on the exchange — the strategy waits for its fill
⚠️ Funding needs clarification Compare the payment with the exchange's statement
⚠️ Your TP price became a loss The fee rose or a new purchase moved the break-even — the strategy went back to the strategy's TP. If you need your own price — set it again on the “TP” screen
⚠️ … little BNB left for fees (and “… for futures fees”) Binance: buy a little BNB (on futures — transfer it to the futures wallet) or switch paying fees in BNB off. The strategies go on working
⚠️ The key of connection … expires in N d Replace the key before that date (Replace the key)
⚠️ … key (…): no trading permission Turn trading on in the key's settings on the exchange, or replace the key
⚠️ DCA level skipped, ⚠️ The lead strategy's command was not applied, ⚠️ The lead strategy's TP price is a loss for the copy, ⚠️ The lead strategy's TP is a loss for the copy, ⚠️ The lead strategy closes the cycle at a loss — the copy too, ⚠️ Manual N: the market buy was not made (a copy's), ⚠️ The exchange refused the manual order (a copy's), ⚠️ Bybit (…): … switched, ⚠️ The key's new term Nothing — they tell what the strategy has already done

✅ — all is fine again

“Funds are enough”, “Order placed”, “Manual N — the order is on the exchange”, “Recovered”, “Trading of the pair is back”, “Funding is read again”, “The lead strategy is back” and others — nothing to do. Such a message closes an earlier 🟠 or ⚠️ about the same thing.

ℹ️ — for your information

Nothing to do unless the last line says otherwise:

  • “Alphafamilia Algo summary” — every morning at 09:00 Madrid time. Its last line says what to do today: open the vault and start the strategies, sort out emergencies — or “Nothing to do.” (How much have I earned);
  • “Start: N”, “Stop: N” — the outcome of a group command with the list of strategies;
  • “Averaging levels cancelled”, “Level restored” — the answer to your “Cancel” and “Restore” in “Levels”;
  • the copy's messages: “The copy began its first cycle”, “The copy waits for the lead strategy's new cycle”, “The lead strategy averaged by hand — the copy too”, “The lead strategy moved the TP — the copy too”, “The lead strategy cancelled levels — the copy too”, “The lead strategy's rules changed”;
  • “Access granted” — your registration request was approved.

The signs of trades and modes

The messages about trades have their own signs and need nothing: 🟢 — a buy filled, 🔵 — a sale, 🟡 — partly filled, 💰 — a cycle closed at the TP (with the profit), ⏹ “Cycle N interrupted” — a cycle closed by “Start a new cycle” or when the strategy was archived (the remainder is yours; if there is one, the last line says to deal with it on the exchange if needed). They can be turned off in the “Notifications” card on the strategy's screen — except the fills of your manual purchases: “🟢 Buy filled: Manual N” always comes.

▶️ ⏸ ⏹ “Strategy started / paused / stopped” — the answer to a command for one strategy. ⏸ is only for a strategy paused earlier: there is no “Pause” button.

🛠 “Обновление Alphafamilia Algo” (an update, in Russian only) goes to the system administrator alone. During an update or a restart a user gets one message, and only when there is something to do: “🔴 Service started” — open the vault and start the strategies; if the vault opened by itself, nothing comes (Server restart).

How to know it worked

  • After a 🟠 or ⚠️ a message with the ✅ sign about the same thing came.
  • After a 🔴 the strategy's screen shows “running”, with no “Waiting”, “Retry … at …” or “Emergency reason” lines.
  • The morning summary ends with “Nothing to do.”.

If something goes wrong

What you see What to do
No “Open the strategy” button The server has just restarted and does not know the app's address yet — open the app with the bot's button in the chat
A 🟠 came, but in the app all is fine It has probably sorted itself out — look for a following message with the ✅ sign
No messages about buys and closed cycles Turn on the switch in the “Notifications” card on the strategy's screen. Emergencies, faults, missing funds and the fills of manual purchases always come
A server message came in Russian although the language is English As designed: the server's messages about an update and a service crash are in Russian only
No messages at all Open the chat with the server's bot and check that the bot is not blocked in Telegram; during a Telegram fault messages wait and come later

Next