⚠️ Critical Flaw for 3Commas users trading via Binance API (Safety Orders Failure)

I’m posting this to warn anyone operating DCA bots on Binance by way of 3Commas API. I’ve been stress-testing the execution logic throughout high-volatility occasions (flash dumps) and located a critical architectural flaw that puts our accounts in danger. The Situation: Restrict Orders vs. Binance Volatility 3Commas at present forces Restrict Orders for all Safety Steps and calculates them based mostly on fastened steps. The State of affairs: When Binance experiences a flash crash (wick down), the worth moves quicker than the order ebook can fill. The Failure: As a result of 3Commas doesn't permit Market Order execution for Safety Orders, the Limit Order will get skipped/gapped. The Outcome: The bot fails to common down. You're left holding a heavy bag with no improved entry worth, while the market tanks -20%. Why this matters: I argued this with their Engineering Group. They admitted internally that their logic is "Improper" and that advanced users want Market execution and "Last Entry" calculation (true Martingale logic), however they're delaying the fix. In case you are trusting your liquidation worth based mostly on the idea that security orders will hit, you want to be careful. The present logic isn't crash-proof. I’ve documented the complete technical breakdown and their admission here (proof): GitHub Technical Report & Dev Response Verify your bot settings. In case you can't select "Market" for security orders, your strategy has a single point of failure.

P.S. To make matters worse: Their Admin just tried to bury this lively report by merging it into a 2-year-old "Completed" thread on their Suggestions Portal (which has nothing to do with this difficulty). They're actively making an attempt to suppress this execution danger quite than fixing it. That is why I am bringing this to the group.

Commerce protected.