What logs should I check if DCA orders are not placed?

If your DCA orders are not being executed in MagicTradeBot, the primary logs to check are the Trade Execution Logs and the Intelligent Decision Logs. These logs provide detailed insights into why an order may not have been triggered, helping you quickly diagnose and resolve issues.

🔹 1️⃣ Trade Execution Logs

  1. Purpose

    • Record all attempts to place trades, including DCA orders
    • Show whether an order was successfully executed, rejected, or skipped

  2. What to Look For

    • Order placement failures: network issues, exchange errors, insufficient balance
    • Skipped orders: when DCA conditions like price_deviation_percent, max_orders, or total_percent_investment_per_trade were not met
    • Execution confirmation: verify if the order was actually sent and acknowledged by the exchange

  3. Typical Log Entries

    [INFO] DCA Order Skipped: Max orders reached for BTC/USDT
[WARN] Order Failed: Insufficient balance to place DCA order
[INFO] DCA Order Executed: BTC/USDT 0.001 BTC at $27,500

🔹 2️⃣ Intelligent Decision Logs

  1. Purpose

    • Record the bot’s internal decision-making process for DCA orders
    • Show why a trade was considered, delayed, or ignored based on strategy logic

  2. What to Look For

    • Signals or conditions not met (e.g., price deviation, cooldown, volatility thresholds)
    • Auto-calculated DCA order size too small or exceeds limits
    • Conflicts with other rules (e.g., Smart Stop-Loss, max loss per trade)

  3. Typical Log Entries

    [DEBUG] DCA Check: BTC/USDT deviation 3% < required 5%, order skipped
[DEBUG] Calculated DCA Order Size $12.50 within max allowed $50
[DEBUG] Market conditions do not satisfy DCA entry rules for ETH/USDT

🔹 3️⃣ Steps to Diagnose

  1. Verify DCA Settings

    • enabled flag in dca.yaml or market_watch.yaml
    • max_orders, size_multiplier, price_deviation_percent, and total investment limits

  2. Check Trade Execution Logs

    • Confirm if the DCA order was attempted
    • Look for errors or warnings preventing placement

  3. Check Intelligent Decision Logs

    • Review why the bot skipped or delayed a DCA order
    • Ensure all preconditions for DCA are met

  4. Cross-Reference

    • Compare intelligent decisions with execution results to pinpoint the issue

🔹 4️⃣ Key Takeaways

  • Trade Execution Logs: Confirm actual placement and execution status
  • Intelligent Decision Logs: Understand the bot’s reasoning behind skipped or delayed orders
  • Combined Review: Provides full insight into why DCA orders may not be placed
  • Critical for troubleshooting both normal and market volatility-based DCA orders

In short, always check both execution and decision logs to diagnose DCA issues effectively, ensuring your settings and market conditions align for proper order placement.

📎 Related Topics