Skip to content
Reference

Troubleshooting

Solutions to common integration, execution, and assistant problems in VarianTrade.

Full documentation context

Overview

This guide provides resolutions for common issues encountered when configuring brokers, receiving signals, running AI connections, or operating the CLI companion.

Broker Integration Issues

Broker Not Linked Warning

If you receive an integration warning when trying to enable auto-trading or place order proposals:

  1. Send /broker in Telegram to initiate the broker configuration flow.
  2. Ensure you have selected a supported broker (MetaTrader 5).
  3. If the connection fails, verify your API keys or login details are correct and have not expired.

Signal Delivery Issues

Proactive Signals Not Arriving

If you are not receiving real-time signal notifications in Telegram:

  1. Verify that your alerts are active. Run /signals in Telegram.
  2. If signals are muted, run /signals on to turn on push notifications.
  3. Check if your account subscription has expired or run out of message credits using /usage.
  4. You can pull the latest active signals manually at any time by running /signals.

Auto-Trading Execution Issues

Auto-Trade is Enabled but Not Executing Trades

If auto-trading is turned on using /resume but no trades are placed:

  1. Risk Limit Filters: VarianTrade passes every signal through your active risk controls before sending it for execution. If a signal exceeds your maximum position size, daily drawdown, or default stop-loss constraints, the trade is blocked to protect your capital.
  2. Run /status in Telegram to inspect your active risk configuration and drawdown metrics.
  3. Check your broker’s connection status. If the broker is offline, auto-trading will pause.

AI Connection Issues

Remote MCP Connector Fails to Load

If your external AI editor (e.g. Cursor or Claude Desktop) cannot connect to VarianTrade:

  1. Ensure the remote MCP URL is entered exactly as: https://api.variantrades.com/mcp/rpc.
  2. Verify that your external AI application and plan support remote MCP server integrations.
  3. Check your Telegram bot chat for a pending authorization prompt. You must tap Approve in Telegram to authorize the connection scopes.

Provider API Key Fails to Enroll

If your API key connection does not activate:

  1. Ensure you selected Add API key within a private chat with the bot. Key enrollment is restricted in public or group chats for security.
  2. Verify that the key has not expired and has sufficient billing balance with the provider (OpenAI, Anthropic, DeepSeek, or Gemini).
  3. VarianTrade deletes the key message immediately upon receipt. If validation fails, delete the message manually if it is still visible, then restart the flow.

CLI Companion Issues

Companion App is Not Executing Jobs

If the local companion (variantrade-bridge) is running but does not process tasks:

  1. Verify Path: Run variantrade-bridge providers on your machine to check if the companion can locate your provider CLI (e.g. claude CLI).
  2. Authentication Status: Ensure you are signed into the provider CLI directly on your machine. The companion does not log you in or store passwords.
  3. Verify Connection: Run variantrade-bridge status to verify local enrollment status and check if the VarianTrade server is reachable.
  4. Queue Check: The companion processes jobs one at a time. Check if a previous job is still running or has timed out.

Contacting Support

If you cannot resolve an issue, you can open a support ticket directly from Telegram:

  • Run /complaint in the bot chat.
  • Submit a detailed description of the problem and attach any screenshots if relevant.
  • Once open, the chat enters ticket routing mode, sending your messages directly to a support agent.
  • Run /close to close the ticket after the issue is resolved.