Troubleshooting

This page collects the issues that come up most often, with a way to check each one. Because Trader Pending works directly in your exchange account through your own API key, most problems trace back to settings on the exchange side. Work through them one at a time, starting with the most common.

API key will not connect

If the connection to the exchange fails or your positions do not appear, check your API key in the exchange dashboard.

• READ and TRADE permissions enabled. The API key needs both read and trade permissions. Without TRADE, orders cannot be sent. You do not need, and should not enable, Withdraw permission.
• IP whitelist matches. If you restrict the key to specific IP addresses on the exchange, make sure the correct address is on the list. When in doubt, remove the IP restriction to test, then reapply it once the connection works.
• Correct exchange selected. Make sure the key is entered under the matching exchange. A Bybit key will not work if it is added as a Binance key.
• Key has not expired. Some exchanges set an expiry on API keys. If it has passed, create a new key and update it in your settings.

Order rejected

If an order fails to send or is rejected by the exchange, the cause is almost always a limit on the exchange side, not the system.

• Insufficient margin. The balance in your exchange futures account must be enough to open the position at the chosen size and leverage. The position-size calculator shows the required margin before you send the order.
• Leverage or step-size limits. Each pair has its own maximum leverage and size increment (step-size). Order size is rounded to the allowed increment; if leverage exceeds the pair limit, lower it first.
• Symbol not listed on that exchange. Not every pair is listed on every exchange. If a symbol is not available on the exchange you selected, choose another exchange that lists the pair.

Stop-loss and take-profit behaviour

Stop-loss and take-profit are handled differently. Understanding this avoids confusion when you watch a position.

• Stop-loss sits on the exchange. The stop-loss is placed as an order directly on the exchange, so it stays in effect even if the bot connection drops.
• Take-profit runs automatically. Take-profit is run by the system, including partial closes when you set more than one target. Because it runs automatically, take-profit depends on the system being active when price is reached.
• Check the position after editing. If you change the stop or target on a running position, confirm the new value is reflected in the positions panel before moving on.

Telegram and web out of sync

Telegram and the web app are two faces of the same system. If they look different, they most likely are not linked as one account yet.

• Link your accounts. Your Telegram and web accounts can be linked so that settings, positions, and balance stay consistent on both sides. Once linked, an action on one side is reflected on the other.
• Reload the view. If a change has not appeared, refresh the web app so it pulls the latest data.

Webhook alert did not fire

If an alert from TradingView does not trigger an order, trace the chain from alert to execution.

• Token is correct. The webhook URL must use your exact token. A wrong or swapped token causes the alert to be rejected.
• JSON payload is valid. The alert message must be valid JSON in the expected format. A misplaced bracket or comma stops the payload from being read.
• Plan supports webhooks. Make sure your plan includes the webhook feature.
• Exchange key connected. An alert can only execute if the exchange API key is connected and working. If the connection is failing, resolve the API key section above first.

Crypto futures trading carries high risk. Trader Pending does not promise profit and does not hold your funds; they stay in your own exchange account.