Telegram troubleshooting
Start by checking the account label, wallet, network and time of the message. An old Activity entry is not necessarily the bot’s current state.
| What you see | Meaning and next step |
|---|---|
| Copy Feed paused after five minutes | The display session ended. Tap Resume live. Check /copy separately for Auto Copy. |
| Starting | The process is not yet confirmed ready. Wait, refresh /copy, and check Activity before trying another start. |
| Auto Copy blocked / execution readiness not confirmed | New buys can be prevented. Read the latest status and reason; report a persistent readiness warning to support rather than repeatedly starting. |
| Running, but no trades | Running alone does not prove eligible signals arrived. Check list members, future buys, filters, signal age, balance and Activity skips/failures. |
| 1 tap OFF after switching accounts | Authorization belongs to the selected context. Review and enable for the current wallet if wanted. |
| Start or trade button expired/already used | Open a fresh /copy, /feed or trade card. Check current status before repeating a money action. |
| Insufficient balance / gas | Check the selected wallet’s native balance. Reserve gas as well as the trade spend; a token balance cannot pay native gas. |
| Route deductions exceed safety limit / fee shortfall | The route failed an execution check. Read the quote/error; do not assume raising slippage makes it acceptable. |
| Worker/tunnel unavailable | The execution service could not be reached or confirmed. Check Activity and current status; contact support if it persists. This is not a request for your private key. |
| Batch shows failures | Check every item and the final recorded outcome in Batch sale history. A completed batch can contain failed holdings. |
| Submitted / pending / unknown outcome | Inspect Activity and the transaction before retrying. Do not infer that no money moved from a missing response. |
Useful information for support
Provide the affected account type, network, approximate time, action, displayed error and public transaction or reference if available. Screenshots should exclude unrelated chats and personal account information.
Never send a private key, email sign-in code, authenticator code, backup code or Telegram connection code.
For execution states and approval/gas costs, see Error messages. For changing a run without losing its current setup, see Auto Copy.
Last updated on