Skip to main content
All CollectionsTrading Errors & Troubleshooting
Why is my Auto-Close not executed?
Why is my Auto-Close not executed?

Learn why your crypto bot's auto-close feature isn't executing and how to troubleshoot these 6 common trading automation issues.

Pete Darby avatar
Written by Pete Darby
Updated yesterday

Auto-close is an important risk management feature that automatically closes positions after they've been open for a specified period. When your auto-close settings fail to execute as expected, it can leave positions open longer than intended and potentially impact your trading performance. This guide explains the most common reasons why your auto-close might not be working and how to resolve these issues.

Common Reasons

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

  2. Trailing Stop-Loss Only Mode
    You have configured "Use Trailing stop-loss only" under the 'Trailing stop-loss' Base config or Config pools.

  3. Time Condition Not Met
    Your 'Close positions after X time open' value hasn't been met yet.

  4. 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.

  5. Config Pool Settings
    You might have configured the currency in a Config pool in which Auto-close is disabled.

  6. 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 auto-close execution issues:

  • Verify that selling is enabled in your bot settings

  • Check your trailing stop-loss configuration to ensure it's not set to "Use Trailing stop-loss only"

  • Confirm the time condition for your auto-close settings and how long positions have been open

  • Review any signal configurations that might override your auto-close settings

  • Check your Config pool settings if you're using them

  • 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?