Skip to main content
All CollectionsTrading Errors & Troubleshooting
Why is my Shorting not executed?
Why is my Shorting not executed?

Discover why your crypto bot's shorting orders aren't executing and how to troubleshoot these 13 common trading automation issues.

Pete Darby avatar
Written by Pete Darby
Updated yesterday

Shorting in Cryptohopper functions like a buyback mechanism rather than traditional shorting. When you expect a position to make a significant loss, you initiate a Short, and your bot will sell the position. Later, when you believe the price has reached its bottom, you consolidate your short and directly buy back the position. This strategy allows you to minimize losses and potentially profit from market downturns without requiring margin trading. When your shorting functionality doesn't execute as expected, it can prevent you from effectively managing losing positions. This guide explains the most common reasons why your shorting might not be working and provides solutions to address these issues.

Common Reasons

  1. Buying Disabled
    Your bot's 'Buying' is disabled manually on the Dashboard or due to the Triggers you use. Some Marketplace Templates have Triggers configured.

  2. Config Pool Limitations
    You might have configured the currency in a Config pool in which Shorting is not available.

  3. Shorting Not Properly Enabled
    You haven't enabled 'Open short based on strategy' and/or 'Always short instead of sell' in the Base config settings.

  4. Profit Condition Not Met
    Your 'Shorting percentage profit' hasn't been met yet. Please read into the feature 'Use actual profit' under the Shorting settings of your Base config.

  5. No Buy Signal
    Your trading strategy hasn't signaled a buy yet.

  6. Trailing Stop-Short Conditions Not Met
    Your Trailing stop-short settings haven't been met yet. Please read into the feature 'Use actual profit' under the Shorting settings of your Base config.

  7. Auto Remove Shorts Feature Active
    You've enabled 'Auto remove shorts within time' in the Shorting settings of your Base config, resulting in your short positions being removed and the reserved funds of your quote currency to become available again for regular buys.

  8. Loss Protection Active
    You've enabled "Do not buy back on loss' in the Shorting settings of your Base config, resulting in your short positions being removed and the reserved funds of your quote currency to become available again for regular buys.

  9. TradingView Alerts Incompatibility
    Shorting doesn't work with TradingView Alerts. When using TradingView Alerts, new regular positions will be opened.

  10. Restore Position Feature Active
    You've enabled 'Restore position after short' in the Shorting settings of the Base config. This could result in the position using previous Shorting settings than your current Shorting settings. This can be checked on the info screen of the "Open shorts" on the Dashboard.

  11. Position Limit Reached
    You've reached your 'Max open short positions' configured in the Shorting settings of the 'Base config'.

  12. Signal Configuration Interference
    You're using trading signals from the Marketplace and have enabled "Signal configuration' and/or 'Sell signals'. Please read this article for more information.

  13. Other Trading Errors
    You might have other trading errors, please check your trading bot output on the Dashboard for more information.

Troubleshooting Steps

To resolve shorting execution issues:

  • Verify that buying is enabled in your bot settings

  • Confirm that the necessary shorting options are enabled in your Base config

  • Review your profit percentage settings and current market conditions

  • Check your trading strategy for buy signals

  • Verify your trailing stop-short settings

  • Review any time-based auto removal settings

  • Check if you're using TradingView Alerts (which don't support shorting)

  • Confirm you haven't reached your maximum open short positions limit

  • Examine your bot's output log for specific error messages

If you continue to experience issues after checking these common causes, please contact support for further assistance.

Did this answer your question?