Charted notes on freqtrade dry run mode in trading automation: mechanics, waypoints, and the wrecks recorded in production.
Mechanics
freqtrade dry run mode works as a staged transformation — ingest, measure, decide, route. Each stage carries its own failure surface.
Waypoints (Configuration)
Configuring freqtrade dry run mode comes down to a short list of parameters. Vendor defaults fit demonstrations; live deployment deserves its own pass.
Wreck Record (Failure Modes)
freqtrade dry run mode sinks in recognizable ways: silent feed gaps, parameters no longer matching the market, latency spikes at the worst moment.
Navigation Checks (Evaluation)
An honest assessment of freqtrade dry run mode weighs quantitative metrics beside code quality and the attention it demands in production.
Configuration Reference
# Freqtrade Dry Run Mode tested configuration mode: production timeframe: auto risk_limits: max_drawdown: 15 percent max_position: 3 percent monitoring: alert_threshold: 0.5 report_interval: hourly
Parameter Impact
| Parameter | Effect | Trade-off |
|---|---|---|
| timeframe | Signal frequency | Higher means fewer but more reliable signals |
| risk_limit | Maximum exposure | Lower means safer but slower returns |
| lookback | Indicator sensitivity | Longer means smoother but lagging |