Operate safely
Troubleshooting
Find your symptom, read what it means, and what to do.
Note. First, always: check positions and orders directly on the exchange. Don't retry blindly or change several settings at once. Send a bug report while the problem is still visible (
Contact Support).
Connecting an exchange
| You see | What to do |
|---|
| The exchange could not be reached… | The key was not checked. Make sure your server is online and its region is allowed by the exchange |
| The exchange rejected these credentials | Fix the key, secret or passphrase, trade permission, IP allowlist; on Bybit, make sure the key is not read-only. Then ✎ Edit → Save |
| NO CREDENTIALS | Edit the account, enter a valid key and save |
| Position read failing … Invalid IP address | Add your server's public IP to the key's allowlist |
| HEDGE MODE BLOCKED | Close all positions and orders, then switch to Hedge Mode (Connect your exchange) |
| A banner says the exchange locked the account | Contact the exchange. After it unlocks, ✎ Edit → Save |
| Bitunix shows several positions on one pair | Turn Multi-Trade off for that pair on bitunix.com |
A bot isn't trading
| You see | What to do |
|---|
| Nothing in Activity | Check the bot is enabled, on this account and market, and its pairs and filters allow trades |
| Entry data refused — … | Candles or prices aren't ready. Wait, or narrow the pair list |
| Bands not computed yet (warming N/M candles) | Optimized Liq is warming up. See Screener → Optimized Values |
| Process memory limit reached / Live candle capacity limit reached / Exchange request-weight limit reached | Too many pairs for the server or exchange. Narrow the pair list |
| No live price for the symbol | Wrong symbol or quote currency (TV Signal: the {{ticker}} trap) |
| Order rejected: … maximum leverage … | The exchange capped leverage on that pair. Lower it |
| License expired — exit-only mode | Renew. Closing and protection continue meanwhile |
| Enable Stop Loss … to arm a cooldown | Switch the stop loss on, or set both cooldowns to 0 |
| Enabled · Auto-attach off — manual attachment required for new positions. | Attach from Attachable positions, or set Auto-attach to Auto |
Exits and protection
| You see | What to do |
|---|
| TP unavailable | Hover or tap the TP row for the exchange's reason, usually minimum size or a price limit. The app retries |
| TP watched by the app | Keep the server running; the app closes at your target |
| UNPROTECTED | Check the exchange minimum order size and the take-profit settings |
| Paired TP unreachable | Hedge is close to the main size. It resolves as tranches bank profit |
Deals out of sync
| You see | What to do |
|---|
| Not on the exchange — confirming / Closed on the exchange — settling | Wait a few minutes |
| Not re-checked / Syncing with the exchange | Check the exchange, your key and any lock banner |
| Unattributed add / reduce | The exchange size changed without a bot order. If you didn't trade, check the exchange and any other system using the key |
| Positions changed unexpectedly | Make sure no other platform uses the same key (Moving from wickhunter.io) |
Updates
| You see | What to do |
|---|
| Update failed with a reason and Try again | Your version keeps running. Try once more, then send a bug report |
| Release recovery needs attention. Do not start another update. | Don't update. Send a bug report |
| Customer Beta updates are unavailable on this installation. | Contact Support for the update tool |
| 502 Bad Gateway after an update | The app is still starting. Wait a minute and reload |
