Stop-loss orders are a critical risk management tool in cryptocurrency trading, designed to limit potential losses when markets move against your positions. When your stop-loss fails to trigger as expected, it can expose your portfolio to greater risk than intended. This guide explains the most common reasons why your stop-loss orders might not be executing and how to address these issues.
Common Reasons
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.Stop-Loss Timeout Active
You've enabled a 'Stop-loss timeout' in your Stop-loss settings in the Base config or Config pools and the configured period hasn't lapsed yet. You can check this in your trading bot output on the Dashboard.Unconfigured Stop-Loss Values
You don't have configured the input values for the Stop-loss that you use and the input values are shown in grey while they should be shown in black to be taken into account by the bot.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.Config Pool Settings
You might have configured the currency in a Config pool in which Stop-loss is disabled.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 stop-loss execution issues:
Verify that selling is enabled in your bot settings
Check if a stop-loss timeout is active and its remaining duration
Ensure your stop-loss values are properly configured (shown in black, not grey)
Review any signal configurations that might override your stop-loss 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.