critical: Fix EMERGENCY_STOP_PERCENT env var not being loaded (Bug #90)

- Added emergencyStopPercent to getConfigFromEnv() function
- Previously hardcoded -2% was always used instead of .env value
- Root cause of trade cmkf5a2ld00kmqn07hvj351fe closing at -2.03%
  when SL was set at -2.8%
- Entry: $145.05, Exit: $142.11, SL: $140.99
- Emergency stop at -2% = $142.15 triggered, ignoring .env -20% setting

Financial Impact: Trade closed prematurely, missing potential recovery
This commit is contained in:
mindesbunister
2026-01-16 15:10:29 +01:00
parent 46c4ee412c
commit d288bf984c

View File

@@ -636,6 +636,9 @@ export function getConfigFromEnv(): Partial<TradingConfig> {
stopLossPercent: process.env.STOP_LOSS_PERCENT stopLossPercent: process.env.STOP_LOSS_PERCENT
? parseFloat(process.env.STOP_LOSS_PERCENT) ? parseFloat(process.env.STOP_LOSS_PERCENT)
: undefined, : undefined,
emergencyStopPercent: process.env.EMERGENCY_STOP_PERCENT
? parseFloat(process.env.EMERGENCY_STOP_PERCENT)
: undefined,
useDualStops: process.env.USE_DUAL_STOPS useDualStops: process.env.USE_DUAL_STOPS
? process.env.USE_DUAL_STOPS === 'true' ? process.env.USE_DUAL_STOPS === 'true'
: undefined, : undefined,