Bot commands · What the bot did
/lastsignals: each recent signal and what HafizeBot did with it
/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.
- Command
/lastsignals- Who can use it
- VIP members with auto-trading switched on (/autotrade)
- Where
- In your chat with @hafizebot on Telegram
/lastsignals is the first place to look when you wonder "why didn't the bot take that trade?". Typing why does the same. Times are in UTC.
Examples
/lastsignals
Your last signals and what the bot did with each (times in UTC):
Oct 11 09:42 UTC SOLUSDT LONG, strength 3: entered ✅
Oct 11 09:15 UTC XRPUSDT SHORT, strength 1: skipped: below your minimum strength (/setMinStrength)
Oct 11 08:50 UTC ETHUSDT LONG, strength 2: skipped: you already had your maximum open positions (/setPositionLimit)
Oct 11 08:02 UTC DOGEUSDT LONG, strength 2: not placed: your futures wallet did not have enough free margin (lower /setPositionSize or /setPositionLimit, or add USDT)
All results: https://www.hafizebot.com/performance
When Binance refused an order, a link under the list explains that error.
Only the trades the bot opened:
/lastsignals entered
Common reasons and what to do
| The line says | What to do |
|---|---|
| auto-trading was off (/on) | Send /on. |
| below your minimum strength | Intended, or lower /setMinStrength. |
| you already had your maximum open positions | Intended, or raise /setPositionLimit. |
| this coin is on your ban list | Intended, or /unbanCoin. |
| the price was within your same-coin gap | Intended, or lower /setDifference. |
| your Binance account was not connected | Check your key at /app/keys. |
| not enough free margin | Add USDT or lower your size or limit, then /on. |
Questions
What is the difference between "skipped" and "not placed"?
Skipped means your settings said no. Not placed means the bot tried and Binance refused or did not answer; the line gives Binance's reason in plain words.
Are the times in my time zone?
No, in UTC, so they match across members and the performance page. Add or subtract your offset from UTC.
Updated 2026-10-11.
Related commands
- /today/today sums up the last 24 hours on your account: signals entered, signals skipped with the most common reason, orders not placed, and take-profits filled with their realized result and fees.
- /myresults/myresults totals the last 30 days of the bot's own orders on your Binance account: closed trades, their result, fees, liquidations, and the net with liquidations counted against the bot; trades you place yourself are not counted.
- /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.
More help
- Why is the bot not opening any trades?
- Why did Binance refuse my order?
- 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 3 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.