Help & Support: FAQ's

If a signal is not executed, there could be a variety of reasons behind it. All failed or skipped signals will be logged and can be reviewed in the Logs page. Below is a summary of common error messages and their possible causes:

Common Signal Execution Errors

1. Entry Manager Disabled

• What it means: The Entry Manager (also known as Signals Manager) is turned off. No signals will be executed while it is disabled.

• How to fix: Turn it on from the View Bots page. It will automatically be disabled for accounts without an active subscription, so you’ll need to manually enable it after the subscription expires.

2. {PAIR} {SIDE} Bot is OFF or Not Created

• What it means: There is no active bot for the received pair and side. For example, you send a signal for BTCUSDT BUY, but there is no active bot for that pair and side.

• How to fix: Ensure that you have an active bot for the specified pair and side.

3. Insufficient Balance for Order Cost

• What it means: The signal attempts to place an order that exceeds the available balance after accounting for slippage and exchange fees. This can occur when using the PERCENT size type, as it calculates based on the total account balance and not just the available balance.

• How to fix: Double-check the available balance and ensure that the order cost does not exceed your funds. Be mindful of slippage and fees when using market orders.

4. Open Size Too Small for Exchange Rules

• What it means: The order size is below the minimum size set by the exchange. For example, BTCUSDT on Bybit has a minimum order size of 0.001 BTC.

• How to fix: Ensure that the order size complies with the exchange’s minimum size rules.

5. Maximum Positions Reached

• What it means: The number of open positions has reached the maximum limit set for your account.

• How to fix: Review and adjust the maximum open positions setting in the View Bots page.

6. Position Already Open

• What it means: Wick Hunter ignores new signals if there is already an open position for the same pair and side. For instance, if BTCUSDT LONG is open, another BTCUSDT LONG signal will be ignored.

• How to fix: Use DCA signals to adjust or add to your existing position rather than opening a new one.

7. Existing Pending Open Order for the Same Pair and Side

• What it means: A pending order already exists for the same pair and side, so the new signal will be ignored.

• How to fix: Make sure that there are no pending orders before sending new signals.

8. Cooldown Timeout Not Expired

• What it means: Signals are restricted by a cooldown timer to prevent multiple signals from being triggered too quickly. If the cooldown period hasn’t expired, the signal won’t be executed.

• How to fix: Adjust the cooldown timer in the View Bots page or wait for the timer to expire before sending the next signal.

9. Isolation Mode Active

• What it means: Isolation mode restricts excessive margin usage. Signals are ignored if the margin used exceeds the limit set.

• How to fix: Check and adjust your Isolation Mode settings in the View Bots page.

10. Failed to Open Position Due to Exchange Error

• What it means: This is a general error message indicating that there was an unexpected issue with the exchange or API.

  • The API key might be invalid or lack proper permissions.

  • The exchange could be experiencing issues.

  • An unknown error occurred.

• How to fix: Check if the API key has the correct permissions, or check with the exchange for any ongoing issues.

---

What To Do When A Signal is Not Executed:

1. Review the Logs: Always check the Logs page for specific details about why the signal was skipped or not executed.

2. Ensure Proper Configuration: Double-check your signal setup, including the correct pair, side, and risk profile (if using Advanced Mode).

3. Balance & Order Size: Ensure you have sufficient funds for the order and that it meets the exchange's minimum order size requirements.

4. Cooldown Timer: Adjust the cooldown timer to avoid firing multiple signals too quickly.

5. API Key Permissions: Make sure your API key has the appropriate permissions and is correctly set up.

6. Monitor Exchange Issues: Sometimes, the exchange may be facing issues that can affect signal execution. Check the exchange status if necessary.