Bot commands · What the bot did
/why: why HafizeBot is not opening trades on your account
/why checks each thing the bot needs before it trades (VIP, your Binance key, the auto-trading switch, your futures wallet, minimum strength, direction, position limit, bans) and lists your last 5 signals with what the bot did.
- Command
/why- Who can use it
- Everyone
- Where
- In your chat with @hafizebot on Telegram
/why answers "auto-trading is on, so why is nothing trading?". It checks your account against each thing the bot needs and marks every line: ✅ fine, ❌ stops trades, ❔ not readable here. Each ❌ line says how to fix it. Typing whynotrades does the same, and on the website the same list is on your account page under "Why is nothing trading?", after you sign in.
Examples
/why
Why is nothing trading? Each thing the bot needs, checked on your account (✅ fine, ❌ stops trades, ❔ not readable here):
✅ VIP is active (Tier 3).
✅ Your Binance API key is saved, and Binance accepted it at our last check.
✅ Auto-trading is switched on.
❔ We have no reading of your Binance wallet here. The bot trades with the USDT in your Binance USD-M Futures wallet (not Spot or Funding): it needs at least 5 USDT free for one trade. Your HafizeBot balance only buys plans.
❌ Your minimum strength is 5, and none of the 41 signals sent in the last 24 hours was that strong. Lower it with /setMinStrength.
✅ You trade both longs and shorts.
❔ Your position limit is 3 coins at once. We do not count your open positions here; when it is full, the signal lines below say so.
✅ Your ban list has the group TradFi; signals on coins of a banned group are skipped. /banlist shows it.
One thing on this list stops new trades. Fix it, then check again.
Your last signals and what the bot did with each (times in UTC):
Nov 14 09:42 UTC SOLUSDT LONG, strength 3: skipped: below your minimum strength (/setMinStrength)
Nov 14 09:15 UTC XRPUSDT SHORT, strength 1: skipped: below your minimum strength (/setMinStrength)
Every signal: /lastsignals. Your settings: /summary, and /settings to change them.
What each line checks
| Line | It stops trades when | Fix |
|---|---|---|
| VIP | your plan or free trial has ended | /join |
| Binance API key | no key is saved, or Binance refused it at the last check | /app/keys, then /on |
| Auto-trading switch | it is off, or was never set up | /on, or /autotrade the first time |
| Futures wallet | Binance refused your last order for lack of free USDT | move USDT into your USD-M Futures wallet on Binance |
| Minimum strength | no signal of the last 24 hours was strong enough | /setMinStrength |
| Direction | you trade one side and no signal at your strength was on it | /setPositionSide |
| Position limit | you already hold as many coins as your limit | /setPositionLimit, or wait for one to close |
| Bans | every signal that passed was on a banned coin or signal type | /banlist |
| Free trial | never; the line states the trial's size and position caps | a plan lifts them: /join |
Questions
Why does a new account trade so rarely?
Outside the free trial, a new account takes only signals of strength 5, the rarest rating. In September 2026 that was 36 of 4,220 signals, about one a day (the September results, linked from the performance page, list signals by strength). /setMinStrength 3 or lower takes more signals; more trades also means more risk, and no setting promises a profit. Where each setting starts: default settings.
Is the balance on /status the money the bot trades with?
No. The HafizeBot balance on /status is what you sent us to buy plans. The bot trades with the USDT in your own Binance USD-M Futures wallet, which never leaves Binance.
Every line is ✅ and there is still no trade. Why?
The list covers what holds every signal back. A single signal can still be skipped for its own reason, such as your same-coin gap or a Tier 3 limit, and the lines under the list give that reason for each of your last 5 signals; /lastsignals shows 10. Signals also come in bursts, so quiet hours are normal.
Does /why ask Binance anything?
No. It reads our own records: your settings, the signals sent in the last 24 hours, the bot's last key check and what happened to your last orders. That is why the wallet and the open positions can show ❔.
Updated 2026-11-14.
Related commands
- /lastsignals/lastsignals lists your last 10 signals and what the bot did with each, entered or skipped and why, such as your minimum strength, position limit or a refused key; /lastsignals entered lists only the trades it opened.
- /setMinStrength/setMinStrength sets the lowest strength, on HafizeBot's 0 to 5 rating, that the bot trades for you, 5 by default; a higher minimum means fewer, pickier entries, and 0 takes every signal.
- /setup/setup shows a checklist of your account (VIP, Binance key, auto-trading, stop-loss and limits) and ends with the one step to take next, so you always know what is missing before the bot can trade for you.
- /status/status shows your Telegram username and chat ID, whether VIP is active with its tier and end date, whether auto-trading is enabled, your HafizeBot balance for buying plans and your referral code, followed by your next step.
More help
- Why is the bot not opening any trades?
- What does signal strength mean, and what should my minimum be?
- What settings does auto-trading start with?
- Why did Binance refuse my key, and how do I fix it?
- Why was auto-trading switched off for insufficient margin?
- Commands that show what the bot did on your account
- All bot commands
Not a member yet? Try VIP free for 7 days, auto-trading included.
A question this page does not answer? Send /support to @hafizebot, or write to [email protected]. Futures trading carries a high risk of loss; nothing here is investment advice.