Autostop
System Overview
Autostop protects your deposit from significant losses by automatically stopping algorithms and closing positions when specified limits are reached.
The system monitors losses in real-time and executes protective actions without your participation, preventing critical deposit drawdowns.
Two types of autostop available:
On balance — monitors realized and unrealized losses relative to maximum balance
On report — analyzes only realized losses in closed trades over selected period
Autostop on Balance
Operating Principle
Autostop on balance monitors the selected asset balance change and triggers if the sum of realized and unrealized losses exceeds the specified limit.
What is tracked:
✅ Realized loss — closed trades with loss
✅ Unrealized loss — current PnL of open positions
Base balance:
The starting point is the maximum balance value reached since autostop launch. Base balance automatically increases when balance grows, but never decreases.
Example:
Autostop launch: balance 100 USDT → base = 100 USDT
Profitable trade +10 USDT: balance 110 USDT → base = 110 USDT
Loss trade -5 USDT: balance 105 USDT → base remains 110 USDT
Profitable trade +3 USDT: balance 108 USDT → base remains 110 USDT
Current loss relative to base: 110 - 108 = -2 USDT
Configuring Autostop on Balance
1. Create autostop
Open the "Autostops" tab and click "New autostop on balance".
2. Specify name
Enter a clear name reflecting the autostop purpose.
Examples:
"Main deposit protection -50 USDT"
"Emergency stop -100 USDT"
"Scalping protection -20 USDT"
3. Select asset
Specify the quote asset whose balance will be monitored.
Available assets:
USDT
USDC
BTC
ETH
and other quote assets
After selecting an asset, the "Current balance" field will display the complete current balance value of this asset.
⚠️ Important: when launching autostop, the current balance value becomes the base. With each stop and restart of autostop, the base balance updates to the current value at launch time.
4. Select algorithms to stop
Define which algorithms will be stopped when autostop triggers.
By default: autostop stops all existing algorithms. Their quantity and names are displayed in the list.
Option A: Stop specific algorithms
In the "Keywords" field, start typing algorithm name and select one or more from the list.
Result: when autostop triggers, only specified algorithms will stop.
⚠️ Important: new algorithms created after autostop configuration will not be stopped.
Search by partial name:
Enter part of the name (e.g., "Shots") and press "Enter". All algorithms containing these characters in the name will be added to the list.
Option B: Stop all algorithms except selected
Enable "Exclude" checkbox and specify algorithms that should not be stopped.
Result: when autostop triggers, all algorithms will stop except those specified in exclusions.
✅ Advantage: new algorithms will be automatically included in autostop, since they are not in the exclusion list.
Application:
use option A for targeted protection of specific strategies
use option B for comprehensive protection of entire deposit
5. Set maximum loss
Specify the maximum allowable loss relative to base balance.
Whole and fractional numbers can be entered. Positive values are automatically converted to negative.
Examples:
10 — autostop will trigger at 10 USDT loss
50.5 — autostop will trigger at 50.5 USDT loss
100 — autostop will trigger at 100 USDT loss
How loss is calculated
Two types of losses are considered:
Realized loss — losses from closed trades
Displayed in "Reports" section as fixed losing trades.
Unrealized loss — current PnL of open positions
Displayed in "Trades and Positions" tab for each open position.
Formula:
Current loss = Base balance - (Current balance + Unrealized PnL of all positions)
Trigger Examples
Example 1: Only unrealized loss
Base balance: 100 USDT
Max loss: -10 USDT
Current open position: PnL = -10 USDT
Result: autostop triggers even if trade is not yet closed
Example 2: Combined losses
Base balance: 100 USDT
Max loss: -10 USDT
Realized loss: -6 USDT (closed trades)
Unrealized loss: -4 USDT (open position)
Result: total loss = -10 USDT → autostop triggers
Example 3: Partial excess
Base balance: 100 USDT
Max loss: -10 USDT
Realized loss: -6 USDT
Current open position: PnL = -3 USDT
Result: total loss = -9 USDT → autostop does not trigger (less than -10)
6. Configure position behavior
Define what to do with open positions when autostop triggers.
Without panic sell (default)
"Panic sell if triggered" checkbox disabled.
Behavior:
algorithms stop
open positions remain open
positions close by Take Profit, Stop Loss, or manually
Application:
Use when you want to preserve the possibility of price retracement and closing positions with lower loss or even profit.
With panic sell
"Panic sell if triggered" checkbox enabled.
Behavior:
algorithms stop
all open positions immediately close with market orders
doesn't matter how and when positions were opened
⚠️ Important: closure occurs at market price, which can lead to slippage and additional losses.
Application:
Use in critical situations when it's more important to lock in loss than wait for more favorable closing conditions.
7. Save and run
Click "Save and run" to activate autostop.
After launch, the "Autostops" → "On balance" tab displays:
autostop name
monitored asset
base balance
current balance
maximum loss
current loss
number of algorithms under protection
status (active/inactive)
Multiple Autostops
You can create multiple autostops on balance with different settings.
Configuration examples:
Autostop 1: General protection
Asset: USDT
Max loss: -100 USDT
Algorithms: all except "Main Shots"
Panic sell: enabled
Autostop 2: Scalping protection
Asset: USDT
Max loss: -20 USDT
Algorithms: all algorithms with word "Scalp"
Panic sell: disabled
Autostop 3: Futures protection
Asset: USDT
Max loss: -50 USDT
Algorithms: all futures algorithms
Panic sell: enabled
Autostop on Report
Operating Principle
Autostop on report analyzes only realized losses in closed trades over selected time period.
What is tracked:
✅ Realized loss — only closed trades
❌ Unrealized loss — open positions not considered
Key capabilities:
loss analysis over sliding time period
filtering by markets (spot, futures)
filtering by trading pairs
filtering by trade sources (specific algorithms)
Configuring Autostop on Report
The settings window consists of two parts:
Upper part — report analysis parameters and base definition
Lower part — algorithm selection for stopping and loss limit
Upper Part: Report Analysis
1. For last
Select sliding time period for report analysis.
Available options:
Last 1 hour
Last 6 hours
Last 12 hours
Last 24 hours
Last 3 days
Last 7 days
Last 30 days
How sliding period works:
When selecting "Last 24 hours", autostop analyzes trades for the last 24 hours from current moment. The period constantly shifts with time.
Example:
Now 3:00 PM Wednesday → trades analyzed from 3:00 PM Tuesday to 3:00 PM Wednesday
In one hour (4:00 PM Wednesday) → trades analyzed from 4:00 PM Tuesday to 4:00 PM Wednesday
2. Market
Specify market for report analysis.
Options:
"Spot" — only spot trades
"Futures" — only futures trades
Empty field — all markets
3. Symbol
Specify trading pairs for report analysis.
Specification methods:
Specific pairs:
Enter exact pair name: BTC/USDT, ETH/USDT
By quote asset:
Enter only USDT → all pairs with USDT are analyzed (BTC/USDT, ETH/USDT, SOL/USDT, etc.)
Multiple pairs:
Use buttons:
"Paste list" — add pair list from clipboard
"Copy to clipboard" — copy current list
All pairs except selected:
Enable "Exclude" checkbox and specify pairs to exclude from analysis.
Empty field: all trading pairs are analyzed
4. Opened by
Specify trade sources for analysis.
Options:
Specific algorithm:
Enter exact name: "Shots BTC/USDT"
By partial name:
Enter "Shots" → all algorithms with word "Shots" in name are analyzed
Manual trading:
Enter "Manual" → only manual trades are analyzed
Multiple sources:
Enter multiple names separated by comma
Empty field: trades from all sources are analyzed
Lower Part: Action Configuration
5. Keywords
Specify algorithms to be stopped when autostop triggers.
Works similarly to "Keywords" field in autostop on balance:
enter specific algorithm names
enter partial name for group selection
use "Exclude" checkbox to stop all except specified
6. Exclude emulated trades
Enable checkbox to consider only real trades when analyzing reports.
Application:
Use when testing strategies with emulated trades, so autostop reacts only to real trading.
7. Information fields
After configuring parameters, information is displayed:
Algorithms
Number of algorithms selected by keywords and their list.
Trades
Number of trades found in reports by specified criteria (period, market, pairs, sources).
Total
Current total PnL for found trades over specified period.
This value is compared with maximum loss to determine autostop trigger.
8. Max loss
Specify maximum allowable loss for configured report selection.
When this value is exceeded, autostop will trigger and stop selected algorithms.
9. Save and run
Click "Save and run" to activate autostop.
After launch, the "Autostops" → "On report" tab displays:
autostop name
analysis period
filters (market, pairs, sources)
number of found trades
total PnL
maximum loss
number of algorithms under protection
status (active/inactive)
Operating Features
Triggering on Launch
⚠️ Important: if at autostop launch moment the total PnL for found trades is already less than maximum allowable loss, autostop will trigger only after the next trade matching selection criteria.
Example:
Max loss: -50 USDT
Current PnL at launch: -60 USDT
Result: autostop won't trigger immediately, will wait for next trade from selection
Recommendation: check current PnL before launching autostop
Multiple Autostops
You can create multiple autostops on report with different settings.
Configuration examples:
Autostop 1: Scalping protection for 24 hours
Period: last 24 hours
Market: futures
Symbol: all pairs with USDT
Sources: algorithms with word "Scalp"
Max loss: -30 USDT
Algorithms: all scalping
Autostop 2: Spot trading protection for week
Period: last 7 days
Market: spot
Symbol: BTC/USDT, ETH/USDT
Sources: all sources
Max loss: -100 USDT
Algorithms: all spot
Autostop 3: Manual trading control
Period: last 3 days
Market: all
Symbol: all
Sources: Manual
Max loss: -50 USDT
Algorithms: all algorithms
Autostop Types Comparison
What is tracked
Realized + unrealized losses
Only realized losses
Reaction to open positions
✅ Yes
❌ No
Time period
Since launch
Sliding period
Filtering
Only by asset
By market, pairs, sources
Base balance
Maximum since launch
Calculated by selection
Application
General deposit protection
Specific strategy control
Usage Tips
When to Use Autostop on Balance
✅ For general deposit protection from critical drawdowns
✅ When it's important to consider open positions
✅ For quick reaction to unrealized losses
✅ When working with high-leverage trading
When to Use Autostop on Report
✅ For controlling specific strategy effectiveness
✅ When detailed parameter filtering is needed
✅ For analyzing results over specific period
✅ When separation of different trading type control is necessary
Combined Protection
For maximum protection, use both autostop types simultaneously:
Autostop on balance:
Asset: USDT
Max loss: -200 USDT
Algorithms: all
Panic sell: enabled
Autostop on report 1:
Period: 24 hours
Max loss: -50 USDT
Sources: scalping algorithms
Algorithms: only scalping
Autostop on report 2:
Period: 7 days
Max loss: -100 USDT
Sources: all algorithms
Algorithms: all
Result: three-level protection with different sensitivity
Common Mistakes
❌ Too small loss limit
Autostop triggers from normal market fluctuations
✅ Solution: set limit considering expected volatility (3-5% of deposit)
❌ Forgot to enable panic sell
When autostop triggers, open positions continue accumulating losses
✅ Solution: enable panic sell for critical situations
❌ Too wide period in autostop on report
Autostop doesn't react to short-term drawdowns
✅ Solution: use short periods (24 hours) for active strategies
❌ Didn't check algorithm list
Autostop stops wrong algorithms or misses needed ones
✅ Solution: carefully check algorithm list before launch
Additional Information
State Preservation
When MoonTrader core restarts, autostop state is preserved:
enabled autostops remain enabled
disabled autostops remain disabled
base balances are saved
settings are not reset
Connection with Other Functions
Trading Efficiency Filters
Autostop on report functionality overlaps with efficiency filters at individual algorithm level. For more details, see "Trading Efficiency" article.
License Autostop
Additional protection type related to license limitations. For more details, see "License Autostop" article.
Contact and Support
If you have questions about autostop configuration or want to suggest improvements, contact support service.
Last updated