Support · Chapter 13/14
Common errors and how to fix them yourself
No accounts showing, buttons not clicking, dead proxies, a frozen tool, AI out of budget, phones not detected… each error with its cause and step-by-step fix.
3 min read · updated Nov 20, 2026
The fastest way to read an error
- Accounts page → filter Errors → click an account → read that account's own log.
- The first red line tells you which step number failed and why.
- Many accounts failing at the same step = the website changed or the script is wrong. Only 1–2 accounts = a problem with those accounts (proxy, password, locked).
💡 Turn on the
Night doctor (
AI hub): in the morning you get a diagnosis and a patch for repeated errors.
Connection and accounts
| Symptom | Usual cause | Fix |
|---|
| Accounts table is empty | GPM not connected / wrong group / wrong mode | Open GPM Login first → Start page → pick the group → Connect & load |
| "GPM NOT connected" | GPM not open or wrong API address | Open GPM, check the API address under Run & settings |
| Mode A/B shows no accounts | No Excel file picked, or the file is open in Excel | Close Excel and pick the file again |
Scripts
| Symptom | Fix |
|---|
| "Element not found" | The page hasn't loaded → add Wait for element before that step; or the XPath changed → press 🎯 to pick it again; buttons with fixed text → use Click by TEXT on the button |
| Clicks the wrong button | The XPath is too generic. Pick it again with 🎯 or use the button text |
| Missing "End if" | Every If… needs exactly one End if |
| Wrong data typed | The name in {@Column} must match the Excel column header exactly (including case) |
| Works on 1 account, fails on many | Lower the threads, increase Spacing, check the proxies |
Proxy and network
| Symptom | Fix |
|---|
| Account fails right when opening the page | Dead proxy → Test proxy, replace dead ones |
| Duplicate IPs | Manual IP rotation with duplicate checking; check your proxy provider |
| Firefox has no internet after a run | Accounts page → Repair network for the ticked accounts |
- See a line "⏱ Tool busy X seconds" → send that line to support.
- Lower the threads; close some browsers; on a low-RAM PC run fewer threads.
- Don't press Run in the web interface and the classic window at the same time.
AI
| Message | Fix |
|---|
| "No key" / "no API address" | AI assistant → Settings, enter the key or remove that worker from Job assignment |
| "Over budget" | The USD/day limit is reached, only free workers remain. Raise the budget or wait until tomorrow |
| AI clicks the wrong button | Check steps labelled ⚠ / ❓ and fix by hand; or describe more precisely (the text on the button) |
| Telegram bot is silent | Is Enable ticked, is the token right; some networks block Telegram |
Phones
| Symptom | Fix |
|---|
| No phone detected | Turn on USB debugging; change the cable (charge-only cables carry no data); change the port |
| "Not allowed" | Unlock the screen → tick Always allow |
| "Disconnected" | Replug, or Restart ADB in the connection assistant |
| Phone has no internet after the tool closed suddenly | Reopen the tool → Remove proxy |
Need support?
AI hub → Customer support → Diagnostic pack: creates a zip (version, settings with keys removed, masked logs, no account data) to send to the seller.