[{"data":1,"prerenderedAt":174},["ShallowReactive",2],{"live-categories":3,"article-tradingview-webhook-mt5":34,"related-tradingview-webhook-mt5":80,"cat-name-mt5":165},{"categories":4},[5,11,15,19,23,26,30],{"slug":6,"sort":7,"name":8,"description":9,"metaTitle":9,"metaDescription":9,"articles":10},"risk-management",1,"Risk Management",null,2,{"slug":12,"sort":10,"name":13,"description":9,"metaTitle":9,"metaDescription":9,"articles":14},"prop-firms","Prop Firms",5,{"slug":16,"sort":17,"name":18,"description":9,"metaTitle":9,"metaDescription":9,"articles":10},"tradingview",3,"Tradingview",{"slug":20,"sort":21,"name":22,"description":9,"metaTitle":9,"metaDescription":9,"articles":17},"mt5",4,"Mt5",{"slug":24,"sort":14,"name":25,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},"crypto-exchanges","Crypto Exchanges",{"slug":27,"sort":28,"name":29,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},"strategies",6,"Strategies",{"slug":31,"sort":32,"name":33,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},"comparisons",7,"Comparisons",{"id":35,"status":36,"publishedAt":37,"updatedAt":37,"author":38,"authorSlug":39,"coverId":9,"coverUrl":9,"ogImageUrl":9,"languageCode":40,"slug":41,"title":42,"excerpt":43,"body":44,"metaTitle":45,"metaDescription":46,"readingTime":47,"headings":48,"category":20,"midCtaAfterBlock":79},"fa0a7493-0cdf-4432-92f9-14794bafaa9c","published","2026-10-02T14:06:00.000Z","Michael Novik","michael-novik","en-US","tradingview-webhook-mt5","TradingView Webhook to MT5: A Setup That Survives a Reboot","Most TradingView-to-MT5 setups work until the VPS restarts. Here's what has to come back on its own afterwards, and how to check it did before your next alert fires.","\u003Cp>The setup works on Tuesday. On Wednesday night Windows installs an update and restarts the VPS. On Thursday morning MT5 is still closed, nobody has noticed, and three alerts have fired into a terminal that wasn't there.\u003C\u002Fp>\u003Cp dir=\"ltr\">Nothing was misconfigured. The setup just had no way of coming back on its own.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>A TradingView-to-MT5 setup survives a reboot only if the machine brings itself back without you: Windows signs in automatically, MT5 starts on its own, the chart with the connector reopens, and algorithmic trading is still switched on. Each link is set once. Then you test the whole chain by rebooting on purpose, before an unplanned restart does it for you.\u003C\u002Fstrong>\u003C\u002Fp>\u003Ch2 id=\"section-0\" dir=\"ltr\">What actually goes down when the VPS restarts?\u003C\u002Fh2>\u003Cp dir=\"ltr\">Execution. Not your alerts.\u003C\u002Fp>\u003Cp dir=\"ltr\">With Vectorhelm, TradingView sends alerts to our servers, not to your VPS. That address never changes and doesn't go offline when your machine does. What stops during a restart is the last step, the connector in MT5 placing the order at your broker.\u003C\u002Fp>\u003Cp dir=\"ltr\">That matters for two reasons. Alerts that fire while MT5 is down are discarded rather than saved and fired later, because a queued entry placed several minutes late is a trade at a price your strategy never saw. And your open positions keep their protection, because a stop loss and take profit placed with a trade are real orders sitting at your broker, which executes them whether your VPS is up or not.\u003C\u002Fp>\u003Cp dir=\"ltr\">Compare that with setups where the alert receiver runs on the VPS itself, usually a local app behind a tunnel. Those lose both halves. The alert arrives at nothing, and when the tunnel restarts it can come back at a different address, so every alert in TradingView is pointing at the old one until you notice.\u003C\u002Fp>\u003Cp dir=\"ltr\">The \u003Ca href=\"\u002Fblog\u002Ftradingview\u002Ftradingview-automation-end-to-end\u002F\">full path an alert travels\u003C\u002Fa> has more places to break than this. The reboot is just the most common one.\u003C\u002Fp>\u003Ch2 id=\"section-1\" dir=\"ltr\">The one-time setup inside MT5\u003C\u002Fh2>\u003Cp dir=\"ltr\">Two permissions, a chart, and a code.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Allow algorithmic trading.\u003C\u002Fstrong> The AutoTrading button on the toolbar, or Tools → Options → Expert Advisors.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Allow DLL imports for the connector.\u003C\u002Fstrong> You can tick it in the connector's own settings when you attach it to a chart, or for the whole terminal in the same Expert Advisors tab.\u003C\u002Fp>\u003Cp dir=\"ltr\">Then attach the connector to any chart (the symbol doesn't matter) and enter the pairing code from your account. That's done once. The connector reconnects on its own after every MT5 restart, VPS reboot or chart reload, and a new code is only needed if you disconnect the account on purpose, revoke the device, or move to a different terminal.\u003C\u002Fp>\u003Cp dir=\"ltr\">The account itself needs to be a hedging account. The connector never changes your terminal's settings, and nothing else under Tools → Options needs touching.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Ca href=\"\u002Fblog\u002Fmt5\u002Fmt5-automation-no-code\u002F\">What gets installed and why\u003C\u002Fa> covers the connector in more detail.\u003C\u002Fp>\u003Ch2 id=\"section-2\" dir=\"ltr\">Making the VPS bring itself back\u003C\u002Fh2>\u003Cp dir=\"ltr\">Four links, and a reboot breaks the chain at whichever one you skipped.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>1. Windows has to sign in by itself.\u003C\u002Fstrong> Programs in the Startup folder only start when someone signs in. After an unattended reboot nobody does, so nothing starts, and the VPS sits at the sign-in screen until you connect to it. Turn on automatic sign-in. Use Microsoft's own Autologon tool rather than the registry method in many VPS guides, which leaves your Windows password sitting in plain text.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>2. MT5 has to start by itself.\u003C\u002Fstrong> Put a shortcut to MT5 in the Startup folder. Type \u003Ccode dir=\"ltr\">shell:startup\u003C\u002Fcode> into the Run box (Windows key + R) to open it. If you run several terminals, each one needs its own shortcut.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>3. MT5 has to log in and reopen the chart.\u003C\u002Fstrong> Tick \"Save password\" when you log into your trading account, so the terminal reconnects without asking. MT5 reopens the charts it had the last time it was closed properly. That last word matters: a forced reboot kills MT5 rather than closing it, and anything you changed since the last clean close can be gone. So after you attach the connector, close MT5 normally once and reopen it. If the chart comes back with the connector on it, the setup is saved.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>4. Algorithmic trading has to still be on.\u003C\u002Fstrong> MT5 remembers the AutoTrading button, but it has settings that switch it off by themselves. The usual one is \"Disable algorithmic trading when the account has been changed,\" under Tools → Options → Expert Advisors. Log into a second account on that terminal, even briefly, and algorithmic trading quietly turns off for both.\u003C\u002Fp>\u003Ch2 id=\"section-3\" dir=\"ltr\">The mistake that looks like a crash\u003C\u002Fh2>\u003Cp dir=\"ltr\">Signing out of the VPS.\u003C\u002Fp>\u003Cp dir=\"ltr\">When you're done on the remote desktop, close the window. Don't choose Sign out. Closing the window leaves your Windows session running, with MT5 inside it. Signing out ends the session and closes every program in it, MT5 included.\u003C\u002Fp>\u003Cp dir=\"ltr\">A good share of \"my EA stopped overnight\" stories are this, and nothing in any log says so. The terminal didn't crash. You closed it.\u003C\u002Fp>\u003Ch2 id=\"section-4\" dir=\"ltr\">Restarts you don't choose\u003C\u002Fh2>\u003Cp dir=\"ltr\">Three kinds, and you can only schedule one of them.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Windows updates.\u003C\u002Fstrong> Set update restarts to happen outside your trading hours, ideally at the weekend when forex is closed. Many VPS providers manage updates for you, so ask yours who controls the schedule before you assume you do.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>MT5 updates itself.\u003C\u002Fstrong> When a new build arrives, the terminal downloads it, closes and reopens. The connection drops for a moment and comes back on its own, which is exactly the case auto-start can't help with and pairing persistence covers.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Provider maintenance.\u003C\u002Fstrong> Hardware moves and host reboots happen on the provider's schedule. Most announce them. Read the emails.\u003C\u002Fp>\u003Ch2 id=\"section-5\" dir=\"ltr\">How do you know it came back?\u003C\u002Fh2>\u003Cp dir=\"ltr\">The connector reports three things separately, because each one fails for a different reason and has a different fix.\u003C\u002Fp>\u003Ctable style=\"min-width: 75px;\">\u003Ccolgroup>\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003C\u002Fcolgroup>\u003Ctbody>\u003Ctr>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>What's reported\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>If it's off\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>Fix\u003C\u002Fp>\u003C\u002Fth>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Connected to Vectorhelm\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>MT5 isn't running, the chart is closed, or the VPS has no internet\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Start MT5, check the chart, check the VPS\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Terminal connected to the broker\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>MT5 is open but not logged in, or the broker's server is down\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Log in, check the account and server\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Algorithmic trading allowed\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>MT5 is connected but AutoTrading is off\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Switch AutoTrading back on\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp dir=\"ltr\">The third one is the one people miss. A terminal that's connected and logged in, with algorithmic trading switched off, looks perfectly healthy until you notice nothing is trading. It shows up as its own state, connected but trading disabled in MT5, rather than letting it pass for a dropped connection or for a quiet market.\u003C\u002Fp>\u003Cp dir=\"ltr\">Both directions are recorded. The activity log notes when the connection dropped and why, and when it returned. On reconnect, any trades your broker executed while the terminal was offline, such as a stop or target being hit, are recovered, and the reconnection entry says how many. You get the account as it actually is, not as it was before the gap.\u003C\u002Fp>\u003Ch2 id=\"section-6\" dir=\"ltr\">Why MetaTrader's built-in VPS won't work for this\u003C\u002Fh2>\u003Cp dir=\"ltr\">Most MT5 guides recommend MetaQuotes' own virtual hosting first, because it's one click from inside the terminal. For this setup it's the one option that can't work.\u003C\u002Fp>\u003Cp dir=\"ltr\">MetaQuotes' rules for its hosting state that no DLLs are allowed on the virtual terminal, and that a program which tries to call one is stopped immediately. The connector needs DLL imports. So it needs an ordinary Windows VPS from any provider, or your own machine.\u003C\u002Fp>\u003Cp dir=\"ltr\">Better to know that before paying for a month of hosting.\u003C\u002Fp>\u003Ch2 id=\"section-7\" dir=\"ltr\">Test it before it matters\u003C\u002Fh2>\u003Cp dir=\"ltr\">Reboot the VPS on purpose. Pick a weekend, or pause your strategies first.\u003C\u002Fp>\u003Cp dir=\"ltr\">Then time it. How long until Windows has signed in, MT5 is open and logged in, and all three states are back? Check the activity log shows the drop and the return. If any link didn't come back, you've found it on your schedule rather than the market's.\u003C\u002Fp>\u003Cp dir=\"ltr\">A setup you've never rebooted is a setup you haven't tested.\u003C\u002Fp>\u003Ch2 id=\"section-8\" dir=\"ltr\">The honest limitation\u003C\u002Fh2>\u003Cp dir=\"ltr\">All of this shortens the gap. It doesn't remove it.\u003C\u002Fp>\u003Cp dir=\"ltr\">Even a perfect setup is a few minutes without execution while Windows restarts, signs in and launches MT5. Alerts in that window are gone. Your stops are safe at the broker, but nothing new opens and no limit that needs the connection can act until it returns.\u003C\u002Fp>\u003Cp dir=\"ltr\">If your strategy can't afford a few minutes of absence at certain hours, around a session open, say, the answer is scheduling restarts away from them, not a cleverer setup. And the VPS stays a single point of failure however well it's configured. That's a property of MT5, which only connects through a terminal. Crypto exchange accounts connect without anything running on your side and need none of this.\u003C\u002Fp>\u003Ch2 id=\"section-9\" dir=\"ltr\">Before you leave it running\u003C\u002Fh2>\u003Cp dir=\"ltr\">Set up automatic sign-in, the Startup shortcut and \"Save password\" once. Close MT5 normally and reopen it to make sure the chart comes back with the connector. Check the setting that turns off algorithmic trading on account change. Close the remote desktop window instead of signing out.\u003C\u002Fp>\u003Cp dir=\"ltr\">Then reboot on purpose and watch all three states come back.\u003C\u002Fp>\u003Cp dir=\"ltr\">Vectorhelm takes \u003Ca href=\"\u002Fsolutions\u002Ftradingview\u002F\">TradingView alerts\u003C\u002Fa> on its own servers and routes them to \u003Ca href=\"\u002Fintegrations\u002Fmetatrader-5\u002F\">your MT5 account\u003C\u002Fa> through the connector, reporting each of the three states separately so a quiet terminal never passes for a quiet market. It isn't open yet. Early access is here if you want it when it is.\u003C\u002Fp>\u003Chr>\u003Cp dir=\"ltr\">\u003Cem>Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice, and no automation setup prevents losses.\u003C\u002Fem>\u003C\u002Fp>","TradingView Webhook to MT5 That Survives a Reboot","A TradingView webhook to MT5 setup that comes back on its own after a VPS reboot, Windows update or MT5 update, and how to test it before it matters.","7 min read",[49,52,55,58,61,64,67,70,73,76],{"id":50,"text":51},"section-0","What actually goes down when the VPS restarts?",{"id":53,"text":54},"section-1","The one-time setup inside MT5",{"id":56,"text":57},"section-2","Making the VPS bring itself back",{"id":59,"text":60},"section-3","The mistake that looks like a crash",{"id":62,"text":63},"section-4","Restarts you don't choose",{"id":65,"text":66},"section-5","How do you know it came back?",{"id":68,"text":69},"section-6","Why MetaTrader's built-in VPS won't work for this",{"id":71,"text":72},"section-7","Test it before it matters",{"id":74,"text":75},"section-8","The honest limitation",{"id":77,"text":78},"section-9","Before you leave it running",24,{"related":81},[82,107,141],{"id":83,"status":36,"publishedAt":84,"updatedAt":84,"author":38,"authorSlug":39,"coverId":9,"coverUrl":9,"ogImageUrl":9,"languageCode":40,"slug":85,"title":86,"excerpt":87,"body":88,"metaTitle":89,"metaDescription":90,"readingTime":91,"headings":92,"category":20,"midCtaAfterBlock":106},"a3850d4f-8aed-46bf-af23-0e75dbdbd3bb","2026-09-21T18:20:00.000Z","mt5-error-4756","MT5 Error 4756: The Number That Tells You Why","4756 doesn't tell you what went wrong. It's a wrapper around a second number printed next to it, and that number is the one with the answer in it.","\u003Cp>You'll find hundreds of pages telling you 4756 means invalid volume. They're wrong, and following them is why people spend an afternoon adjusting lot sizes on an order that was rejected for something else entirely.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>4756 means your broker refused the order. That's all it means. It carries no reason of its own. It's a wrapper, and the actual cause is a second number printed beside it in the log, usually starting with 100. That second number is the one to search for. 10016 is stops placed too close to price, 10014 is an invalid lot size, 10019 is insufficient margin, 10018 is a closed market.\u003C\u002Fstrong>\u003C\u002Fp>\u003Cp dir=\"ltr\">Find the second number and the problem is usually solved in a minute. Without it you're guessing.\u003C\u002Fp>\u003Ch2 id=\"section-0\" dir=\"ltr\">Where the second number is\u003C\u002Fh2>\u003Cp dir=\"ltr\">Open the terminal, go to the Toolbox at the bottom, and look at the \u003Cstrong>Journal\u003C\u002Fstrong> tab, or \u003Cstrong>Experts\u003C\u002Fstrong> if an automated strategy placed the order. Find the line with 4756 in it. The reason code sits on the same line or the one immediately after.\u003C\u002Fp>\u003Cp dir=\"ltr\">If you're running a third-party tool rather than reading the terminal directly, check whether it records the rejection and the reason. Some do, and it saves you the trip.\u003C\u002Fp>\u003Ch2 id=\"section-1\" dir=\"ltr\">What each reason means, and what to do\u003C\u002Fh2>\u003Ctable style=\"min-width: 75px;\">\u003Ccolgroup>\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003C\u002Fcolgroup>\u003Ctbody>\u003Ctr>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>Code\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>Meaning\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>What to do\u003C\u002Fp>\u003C\u002Fth>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10016\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Stops too close to price\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Widen the stop or target. Most common cause\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10014\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Lot size invalid\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Round to the broker's step, check minimum and maximum\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10019\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Not enough margin\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Reduce size or close something\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10018\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Market closed\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Check the symbol's trading hours, not your local clock\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10017\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Trading disabled\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>On the account or the symbol. Contact your broker\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10004\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Requote\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Price moved. Increase allowed deviation\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>10013\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Request invalid\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Something malformed in the order itself\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp dir=\"ltr\">\u003Cstrong>10016 deserves the top spot\u003C\u002Fstrong> because it's the one people never expect. Every broker sets a minimum distance between the current price and where a stop or target is allowed to sit, and it varies per symbol. A stop distance that works fine on EURUSD gets rejected on gold, where the minimum distance is often far wider and the spread widens further around news and the daily rollover. You can check it yourself: press Ctrl+U, pick the symbol, and read the stops level in its specification.\u003C\u002Fp>\u003Ch2 id=\"section-2\" dir=\"ltr\">Why the answers you find don't match your error\u003C\u002Fh2>\u003Cp dir=\"ltr\">Here's the thing nobody explains, and it's why this particular error is so badly covered.\u003C\u002Fp>\u003Cp dir=\"ltr\">There are three different numbering systems describing the same failed order, and they've all been in use at once for years.\u003C\u002Fp>\u003Cp dir=\"ltr\">The old platform used numbers like 130 and 131. The current platform has runtime errors in the 4750s, which is where 4756 lives. And the broker's server has its own set starting at 10004, which is where the real reasons live.\u003C\u002Fp>\u003Cp dir=\"ltr\">A decade of forum answers is written in the first system. So you search your problem, land on a post explaining error 131, and it's correct. But the number on your screen is 10014, and nothing connects the two for you. The conditions didn't change when the platform did. Only the numbering did.\u003C\u002Fp>\u003Cp dir=\"ltr\">That's also how \"4756 means invalid volume\" spread. Someone's 4756 happened to be a volume problem, they wrote it up, and the wrapper got permanently mislabelled with one of the things it can wrap.\u003C\u002Fp>\u003Ch2 id=\"section-3\" dir=\"ltr\">The lot size one, worked properly\u003C\u002Fh2>\u003Cp dir=\"ltr\">If your reason code is 10014, the arithmetic is worth seeing, because the usual advice is to round and move on and that quietly costs you something.\u003C\u002Fp>\u003Cp dir=\"ltr\">Every symbol has a smallest allowed size and a step. On most forex pairs the step is 0.01 lots. On some indices it's 0.1. Your order has to be an exact multiple of that step, and it has to sit between the symbol's minimum and maximum.\u003C\u002Fp>\u003Cp dir=\"ltr\">Now run a normal risk calculation. You want to risk 1% of a $10,000 account, so $100, with a 37-pip stop on EURUSD at about $10 a pip per lot. That's $100 divided by 370, which is 0.27027 lots. Send that and it's refused. Round to 0.27 and it goes through.\u003C\u002Fp>\u003Cp dir=\"ltr\">Fine so far. The problem is at the other end.\u003C\u002Fp>\u003Cp dir=\"ltr\">Take a $2,000 account, the same 1% risk, and a 50-pip stop. That's $20 divided by 500, or 0.04 lots. Still fine. Now the same account with a 200-pip stop: $20 divided by 2,000 is 0.01 lots, exactly the minimum. Drop the account to $800 and the calculation wants 0.004 lots, which is below the minimum entirely.\u003C\u002Fp>\u003Cp dir=\"ltr\">At that point you have two options and most tools quietly pick the first: round up to 0.01 and take two and a half times the risk you intended, or skip the trade. Rounding up is the one that ends accounts, because it doesn't error, it doesn't warn, and every trade after it is sized wrong in the same direction.\u003C\u002Fp>\u003Cp dir=\"ltr\">If your position sizes are near your broker's minimum, check which of those your setup does. It's a more valuable answer than the fix for 10014.\u003C\u002Fp>\u003Ch2 id=\"section-4\" dir=\"ltr\">What a properly built connection does about this\u003C\u002Fh2>\u003Cp dir=\"ltr\">The entire malformed-request class of 4756 is preventable, and it's preventable before the order is sent rather than after it bounces.\u003C\u002Fp>\u003Cp dir=\"ltr\">Vectorhelm reads each symbol's specification from your broker before anything is sent: minimum and maximum order size, the volume step, the allowed filling types, and the minimum distance for stops and targets. Every order is conformed to it first. Size is rounded to the broker's step, so an off-step lot never leaves. An order above the broker's per-order maximum is split rather than refused, so 150 lots against a 100-lot cap goes out as 100 and 50. An order below the minimum is stopped before it's sent, with the reason shown, rather than silently rounded up into more risk than you asked for. The filling type is the one that symbol actually allows instead of a hardcoded default, which is behind a whole category of 4756 reports that have nothing to do with lot size. Stops and targets are placed outside the broker's minimum distance, so 10016 doesn't arise.\u003C\u002Fp>\u003Cp dir=\"ltr\">A trade request built that way is never rejected for being malformed.\u003C\u002Fp>\u003Ch2 id=\"section-5\" dir=\"ltr\">The honest limitation\u003C\u002Fh2>\u003Cp dir=\"ltr\">A broker can still refuse an order for reasons that have nothing to do with how the request was built.\u003C\u002Fp>\u003Cp dir=\"ltr\">Insufficient margin is a real state of your account. A closed market is a real fact about the session. Trading disabled on the account is a decision your broker made. No amount of validation on the way out changes any of those, and anyone claiming their tool eliminates rejections entirely is describing something that doesn't exist.\u003C\u002Fp>\u003Cp dir=\"ltr\">What's reasonable to expect is that each one comes back with the broker's own reason attached, so you know within seconds whether the problem is the order, the account, or the clock.\u003C\u002Fp>\u003Ch2 id=\"section-6\" dir=\"ltr\">The short version\u003C\u002Fh2>\u003Cp dir=\"ltr\">4756 is a label, not a diagnosis. Go and find the number next to it.\u003C\u002Fp>\u003Cp dir=\"ltr\">If it's 10016, widen your stops and check the symbol's minimum distance. If it's 10014, check the step and the minimum, and find out what your tool does when a risk calculation lands below that minimum. If it's 10019 or 10018, the order was fine and something about your account or the session wasn't.\u003C\u002Fp>\u003Cp dir=\"ltr\">And if you're building automation on top of MT5, the fix for the first two isn't something you apply when they happen. It's something that should already have been applied to every order before it left.\u003C\u002Fp>\u003Cp dir=\"ltr\">Vectorhelm conforms every order to the \u003Ca href=\"\u002Fintegrations\u002Fmetatrader-5\u002F\">broker's own symbol specification\u003C\u002Fa> before sending it, and reports anything the broker refuses with the broker's reason attached. It isn't open yet. Early access is here if you want it when it is.\u003C\u002Fp>\u003Chr>\u003Cp dir=\"ltr\">\u003Cem>Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice, and no automation setup prevents losses.\u003C\u002Fem>\u003C\u002Fp>","MT5 Error 4756: What It Actually Means","MT5 error 4756 means your broker rejected the order, not why. The second number next to it carries the reason, and here's what each one means and fixes.","6 min read",[93,95,97,99,101,103,104],{"id":50,"text":94},"Where the second number is",{"id":53,"text":96},"What each reason means, and what to do",{"id":56,"text":98},"Why the answers you find don't match your error",{"id":59,"text":100},"The lot size one, worked properly",{"id":62,"text":102},"What a properly built connection does about this",{"id":65,"text":75},{"id":68,"text":105},"The short version",41,{"id":108,"status":36,"publishedAt":109,"updatedAt":109,"author":38,"authorSlug":39,"coverId":9,"coverUrl":9,"ogImageUrl":9,"languageCode":40,"slug":110,"title":111,"excerpt":112,"body":113,"metaTitle":114,"metaDescription":115,"readingTime":116,"headings":117,"category":20,"midCtaAfterBlock":140},"8103bcad-e206-4ace-b536-3ad2d6facad6","2026-09-09T19:54:00.000Z","mt5-automation-no-code","MT5 Automation With No Code: What You Install and Why","MT5 can't be reached from outside, so automation always means something small running inside your terminal. Here's what that is, what it needs, and what stops when your laptop sleeps.","\u003Cp>You can automate MetaTrader 5 without writing a line of anything. That part of the marketing is true.\u003C\u002Fp>\u003Cp dir=\"ltr\">What the marketing skips is that something still has to run inside your terminal, because MT5 has no way of hearing from the outside world. Understanding that one fact answers most of the questions people ask afterwards, including the expensive one about what happens when your laptop goes to sleep.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Automating MT5 without code means installing a small program in your terminal that connects your account to a platform where you build and run the strategy. You don't write the program and you don't touch it after setup. What you do configure is the strategy, the symbol, and the risk limits, all outside MT5. The trade-off is that your terminal has to stay open and connected, because it's the only door into your account.\u003C\u002Fstrong>\u003C\u002Fp>\u003Ch2 id=\"section-0\" dir=\"ltr\">Why does anything need to be installed at all?\u003C\u002Fh2>\u003Cp dir=\"ltr\">Because MT5 only talks to your broker.\u003C\u002Fp>\u003Cp dir=\"ltr\">The terminal reaches out to your broker's server and holds that line open. That's the whole of its network life. Nothing on the internet can reach in the other direction, place a trade, or ask what your positions are. There's no address to send anything to.\u003C\u002Fp>\u003Cp dir=\"ltr\">So automation has to work from the inside. A small program sits in your terminal, holds the connection to the platform running your strategy, and does the talking in both directions. In MetaTrader's own language that program is an Expert Advisor, which is why every tool in this category involves installing one no matter how the product is described.\u003C\u002Fp>\u003Cp dir=\"ltr\">The \"no code\" part is accurate and worth being clear about: somebody has already written that program, it's the same one for everybody, and you never open it. You install it once and configure everything else somewhere with buttons.\u003C\u002Fp>\u003Ch2 id=\"section-1\" dir=\"ltr\">What do you actually install?\u003C\u002Fh2>\u003Cp dir=\"ltr\">For Vectorhelm it's one file, the Connector EA, and the setup is shorter than most people expect.\u003C\u002Fp>\u003Cp dir=\"ltr\">You download the connector, add it to your MT5 terminal the same way you'd add any Expert Advisor, and run it on a chart. \u003Cstrong>Any chart, any symbol.\u003C\u002Fstrong> The chart it sits on has nothing to do with what you trade. It's just somewhere for the program to live.\u003C\u002Fp>\u003Cp dir=\"ltr\">Then you paste in a pairing code from your account in the client area, and the connection is made. That's the setup.\u003C\u002Fp>\u003Cp dir=\"ltr\">Two things about that are worth pulling out, because they cut against how people expect MT5 automation to work.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>One connector per account, not per strategy.\u003C\u002Fstrong> The usual mental model, inherited from years of buying Expert Advisors, is that each strategy is its own EA on its own chart with its own settings. That's not what's happening here. One connector handles the account, and every strategy you build runs through it. Three strategies or ten, the terminal side is identical.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>The chart symbol is irrelevant.\u003C\u002Fstrong> Leave it on whatever was open. People instinctively attach it to the pair they want to trade and then wonder how to add a second one. You don't.\u003C\u002Fp>\u003Cp dir=\"ltr\">The step-by-step version with screenshots is a separate walkthrough. This page is about the shape of it.\u003C\u002Fp>\u003Ch2 id=\"section-2\" dir=\"ltr\">Does your account have to be hedging?\u003C\u002Fh2>\u003Cp dir=\"ltr\">Yes. Right now this only works on a hedging account, and it's worth understanding why rather than treating it as a compatibility box.\u003C\u002Fp>\u003Cp dir=\"ltr\">MT5 accounts come in two flavours and your broker decides which one you get.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Hedging\u003C\u002Fstrong> treats every trade as its own position. Buy EURUSD twice and you have two positions, each with its own entry, its own stop, its own result. You can hold a long and a short on the same pair at the same time.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Netting\u003C\u002Fstrong> allows one position per symbol and merges everything into it. Buy one lot, then sell half a lot, and you don't have two trades. You have one position, now half the size. Sell more than you're holding and the position flips direction. Everything collapses into a single line with an averaged entry price.\u003C\u002Fp>\u003Cp dir=\"ltr\">If you've traded crypto futures on Binance or Bybit, you already know this distinction under different names. Hedge mode lets a long and a short coexist on the same contract. One-way mode nets them against each other. Same idea, same consequences.\u003C\u002Fp>\u003Cp dir=\"ltr\">For automation, hedging is the one that behaves predictably. Each strategy's trades stay separate and identifiable, stops attach to the position they were meant for, and a second strategy trading the same pair doesn't quietly merge into the first one's position. On a netting account those separations stop existing, and there's no way to reconstruct them afterwards.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>How to check:\u003C\u002Fstrong> ask your broker, or look at your account type in your broker's client area. Most retail forex brokers offering MT5 to non-US clients default to hedging, and several offer both. If yours is netting, opening a hedging account with the same broker is usually a form rather than a negotiation.\u003C\u002Fp>\u003Cp dir=\"ltr\">Do this before you set anything else up. It's the one prerequisite that can't be worked around later.\u003C\u002Fp>\u003Ch2 id=\"section-3\" dir=\"ltr\">How does it know what to trade?\u003C\u002Fh2>\u003Cp dir=\"ltr\">The account tells it.\u003C\u002Fp>\u003Cp dir=\"ltr\">As soon as the connector pairs, it sends your account's own symbol list up to the platform, along with the account's basic state. So when you build a strategy and pick a symbol, you're choosing from what your broker actually offers on your account, not typing a name and hoping.\u003C\u002Fp>\u003Cp dir=\"ltr\">That removes a problem this whole category is normally full of. Brokers name things differently. One shows EURUSD, another EURUSD.raw, another EURUSD_i, and gold might be XAUUSD or GOLD depending on where you signed up. Tools that ask you to type the symbol yourself turn that into a configuration step you can get wrong, usually discovering it when an order is rejected. Selecting from your own account's list means the name is already correct, because it came from there.\u003C\u002Fp>\u003Cp dir=\"ltr\">The same channel carries the trading. When a strategy triggers, the platform sends the instruction down to the connector, the connector places it, and it sends back what happened. So execution is confirmed rather than assumed — the platform knows the fill, not just that it asked for one.\u003C\u002Fp>\u003Cp dir=\"ltr\">That's a genuine difference from the way TradingView alerts work on their own, where a message goes out and nothing comes back. Anything built on that model finds out about a rejected order eventually, or never.\u003C\u002Fp>\u003Ch2 id=\"section-4\" dir=\"ltr\">Can one connection run several strategies?\u003C\u002Fh2>\u003Cp dir=\"ltr\">Yes, and this is the part that changes what's practical.\u003C\u002Fp>\u003Cp dir=\"ltr\">One connection, as many strategies as you want to run on that account. They don't compete for the terminal, they don't need separate charts, and they don't need to be told about each other. The same is true of every account type the platform connects to, not just MT5 — one connection per account, any number of strategies on top.\u003C\u002Fp>\u003Cp dir=\"ltr\">That matters more than it sounds, because it's the difference between adding a strategy and rebuilding a setup. It also means the account-level view is real: something can watch what all of your strategies are doing together, which is impossible when each one is a separate program that only knows about itself.\u003C\u002Fp>\u003Cp dir=\"ltr\">Running five strategies is where risk gets interesting, and where limits at the account level stop being optional. That's its own subject.\u003C\u002Fp>\u003Ch2 id=\"section-5\" dir=\"ltr\">What happens when MT5 closes?\u003C\u002Fh2>\u003Cp dir=\"ltr\">It disconnects, and you should know exactly what that means before it happens rather than during.\u003C\u002Fp>\u003Cp dir=\"ltr\">The connector needs the terminal running and connected. The realistic ways that stops being true:\u003C\u002Fp>\u003Cul dir=\"ltr\">\u003Cli>\u003Cp>Your laptop goes to sleep\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>You close MT5, or close the chart the connector is sitting on\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Your VPS restarts\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>MT5 restarts itself for a forced update, which usually causes a short drop rather than a lasting one\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Ordinary network trouble at your end or your VPS provider's\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp dir=\"ltr\">Vectorhelm detects the drop and notifies you. That's the part worth having, because the failure mode specific to automation is silence — no trades looks identical to no signals, and people have gone a week without noticing.\u003C\u002Fp>\u003Cp dir=\"ltr\">Here's the split that matters while you're disconnected. \u003Cstrong>A stop loss and take profit placed with a trade are real orders sitting at your broker.\u003C\u002Fstrong> They aren't levels the platform watches and closes against. Once they're there, they execute whether your terminal is running, your VPS is up, or anything else is alive. Your open positions keep their protection.\u003C\u002Fp>\u003Cp dir=\"ltr\">What stops is everything that needs the connection: new entries, strategy logic, and any limit that has to see the account to enforce it. Those resume when the connection does.\u003C\u002Fp>\u003Cp dir=\"ltr\">Anyone claiming their cloud platform enforces limits through a disconnection is describing something that can't happen. The honest version is that orders at the broker survive and logic elsewhere doesn't, which is why it matters where your protection was placed in the first place.\u003C\u002Fp>\u003Ch2 id=\"section-6\" dir=\"ltr\">What \"no code\" doesn't give you\u003C\u002Fh2>\u003Cp dir=\"ltr\">You're configuring, not programming, and that boundary is real.\u003C\u002Fp>\u003Cp dir=\"ltr\">You can set what \u003Ca href=\"\u002Fplatform\u002Fsignal-execution\u002F\">triggers a trade\u003C\u002Fa>, which symbol, how size is worked out, where stops and targets go, session rules, and how much a strategy or the whole account is allowed to lose. That covers the large majority of what people actually want to automate.\u003C\u002Fp>\u003Cp dir=\"ltr\">What it doesn't cover is behaviour nobody built a setting for. If your idea depends on a custom indicator's internal values, or on reacting to something between price ticks, no configuration screen reaches it. Find that out early. Discovering it three weeks in means changing approach rather than changing a setting.\u003C\u002Fp>\u003Ch2 id=\"section-7\" dir=\"ltr\">What about prop firm rules?\u003C\u002Fh2>\u003Cp dir=\"ltr\">It's an Expert Advisor in your terminal, and firm rules about EAs apply to it regardless of what the platform around it does.\u003C\u002Fp>\u003Cp dir=\"ltr\">Firms differ more than most traders realise. Some permit automated trading outright with technical caps on activity. Some permit EAs only as risk or trade-management tools and prohibit anything that opens trades on its own. At least one firm treats a tool that merely adjusts stops or sizing as an EA anyway, so its fees and limits apply even to something that never enters a trade. Several allow EAs on MT5 but not on other platforms they offer, which quietly excludes traders who bought the wrong account type.\u003C\u002Fp>\u003Cp dir=\"ltr\">Read the firm's own published policy, ask in writing before you buy a challenge, and keep the answer with a date on it. Rules here change often enough that a forum consensus from last year is worth nothing. The firm-by-firm version is a page of its own.\u003C\u002Fp>\u003Cp dir=\"ltr\">No firm has approved or classified any particular tool, and any page telling you otherwise is selling something.\u003C\u002Fp>\u003Ch2 id=\"section-8\" dir=\"ltr\">What to check before you pick a tool\u003C\u002Fh2>\u003Cp dir=\"ltr\">Four questions separate the tools in this category, and none of them appear on the comparison tables vendors publish about each other.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Does it need one program per strategy, or one per account?\u003C\u002Fstrong> The one-per-strategy model means every new idea is another chart, another install, another set of settings to keep straight, and no single place that sees your total exposure. Ask it as \"if I want to add a fourth strategy next month, what do I do.\"\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Does it confirm what actually happened, or only send instructions?\u003C\u002Fstrong> A tool that fires an order and moves on will show you what it intended. A tool that reads the reply back knows what filled, at what price, and whether anything was rejected. The difference shows up the first time an order doesn't go through, which is when you find out which kind you bought.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Where do your stops live?\u003C\u002Fstrong> If a stop loss is placed as a real order at your broker, it survives your terminal closing, your internet dropping and the vendor having a bad day. If it's a level the tool watches and closes against, none of that is true, and very few products state which one they do. Ask directly, and treat vagueness as an answer.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>What does it do when it can't reach your terminal?\u003C\u002Fstrong> Every tool in this category disconnects sometimes. The useful question isn't whether it happens, it's whether you're told. A setup that goes quiet without telling you is indistinguishable from a market with no setups, and people have lost weeks that way.\u003C\u002Fp>\u003Cp dir=\"ltr\">None of these are hard to ask. They're just not the questions the sales page is written to answer.\u003C\u002Fp>\u003Ch2 id=\"section-9\" dir=\"ltr\">The honest limitation\u003C\u002Fh2>\u003Cp dir=\"ltr\">Your terminal is a single point of failure, and no amount of good design on the platform side removes it.\u003C\u002Fp>\u003Cp dir=\"ltr\">The connection lives where MT5 lives. If that's a laptop you close at night, your automation keeps banker's hours. A VPS fixes the sleep problem and introduces its own. You now depend on a provider you've never spoken to, and you'll find out how good they are during an outage rather than before one.\u003C\u002Fp>\u003Cp dir=\"ltr\">This is inherent to MT5 rather than to any product. Crypto exchange accounts connect over an interface that exists on the internet, so nothing of yours has to stay awake. MT5 has no equivalent, and until it does, automating it means keeping a machine alive.\u003C\u002Fp>\u003Cp dir=\"ltr\">Worth knowing before you build a strategy that assumes continuous coverage.\u003C\u002Fp>\u003Ch2 id=\"section-10\" dir=\"ltr\">Where to start\u003C\u002Fh2>\u003Cp dir=\"ltr\">\u003Cstrong>Confirm your account is hedging.\u003C\u002Fstrong> One message to your broker, and it's the prerequisite everything else depends on.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Decide where the terminal will live.\u003C\u002Fstrong> Your own machine is fine for testing and a bad idea for anything you're not watching. Whether you need a VPS depends on what you're running, and it's a smaller decision than the internet suggests.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Connect one account, run one strategy, and watch it place an entry and take an exit.\u003C\u002Fstrong> Then check your MT5 position list against what the platform says it did. Those two agreeing is what you're testing.\u003C\u002Fp>\u003Cp dir=\"ltr\">\u003Cstrong>Set your \u003C\u002Fstrong>\u003Ca href=\"\u002Fplatform\u002Frisk-management\u002F\">\u003Cstrong>limits\u003C\u002Fstrong>\u003C\u002Fa>\u003Cstrong> before the second strategy, not after.\u003C\u002Fstrong> The point where automation gets away from people is the point where several strategies are running and nothing is watching the total.\u003C\u002Fp>\u003Cp dir=\"ltr\">Vectorhelm connects \u003Ca href=\"\u002Fintegrations\u002Fmetatrader-5\u002F\">MT5 brokers\u003C\u002Fa> and crypto exchanges in one place, with one connection per account and risk limits applied at strategy and account level. It isn't open yet. Early access is here if you want it when it is.\u003C\u002Fp>\u003Chr>\u003Cp dir=\"ltr\">\u003Cem>Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice, and no automation setup prevents losses.\u003C\u002Fem>\u003C\u002Fp>","MT5 Automation With No Code: What You Install","MT5 automation with no code still needs something running in your terminal. What you install, why hedging is required, and what breaks on a drop.","11 min read",[118,120,122,124,126,128,130,132,134,136,137],{"id":50,"text":119},"Why does anything need to be installed at all?",{"id":53,"text":121},"What do you actually install?",{"id":56,"text":123},"Does your account have to be hedging?",{"id":59,"text":125},"How does it know what to trade?",{"id":62,"text":127},"Can one connection run several strategies?",{"id":65,"text":129},"What happens when MT5 closes?",{"id":68,"text":131},"What \"no code\" doesn't give you",{"id":71,"text":133},"What about prop firm rules?",{"id":74,"text":135},"What to check before you pick a tool",{"id":77,"text":75},{"id":138,"text":139},"section-10","Where to start",34,{"id":142,"status":36,"publishedAt":143,"updatedAt":143,"author":38,"authorSlug":39,"coverId":9,"coverUrl":9,"ogImageUrl":9,"languageCode":40,"slug":144,"title":145,"excerpt":146,"body":147,"metaTitle":148,"metaDescription":149,"readingTime":47,"headings":150,"category":27,"midCtaAfterBlock":164},"6379d2da-30b0-4439-8363-e86f43693769","2026-10-15T08:43:00.000Z","tradingview-dca-martingale","TradingView Alert to DCA or Martingale: The Real Numbers","One setting turns a DCA ladder into a Martingale ladder. Here's what each costs at eight rungs, what bounce gets you out, and which limit actually stops it.","\u003Cp>Every page selling a Martingale bot shows you the exit. The ladder goes underwater, the average entry drops, price bounces half a percent, the whole thing closes green. What none of them shows is the size of the position at the moment of that bounce.\u003C\u002Fp>\u003Cp>Here are the numbers, side by side with DCA, because they're the same ladder with one setting changed.\u003C\u002Fp>\u003Cp>\u003Cstrong>A DCA ladder and a Martingale ladder are the same thing: a sequence of entries at set price intervals, closed together at one take-profit above the average entry. The only difference is the multiplier. At 1, every rung is the same size, which is DCA. At 2, every rung doubles, which is Martingale. At eight rungs, doubling needs a 1.5% bounce to exit where equal sizing needs 4.1%, and it holds 32 times the exposure to get it. The limit that stops either one is max drawdown, not daily loss.\u003C\u002Fstrong>\u003C\u002Fp>\u003Ch2 id=\"section-0\">What a ladder actually is\u003C\u002Fh2>\u003Cp>A signal fires and the first order opens. Price falls a set distance, and a second order opens below it. It falls again, a third. Every rung lowers the ladder's average entry, so the price it needs to climb back to in order to close in profit gets nearer with each one.\u003C\u002Fp>\u003Cp>All rungs share one take-profit, set a fixed percentage above the average entry, and the whole ladder closes together when price reaches it. There's no stop-loss on the rungs. The ladder either reaches its take-profit, or you close it, or a risk limit closes it.\u003C\u002Fp>\u003Cp>That last sentence is the whole subject of this article.\u003C\u002Fp>\u003Ch2 id=\"section-1\">One setting, two strategies\u003C\u002Fh2>\u003Cp>Here's a ladder with eight rungs, entries 1% apart starting at 100, and a take-profit 0.5% above the average. The first order is one unit.\u003C\u002Fp>\u003Ctable style=\"min-width: 75px;\">\u003Ccolgroup>\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003Ccol style=\"min-width: 25px;\">\u003C\u002Fcolgroup>\u003Ctbody>\u003Ctr>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>Multiplier 2 (Martingale)\u003C\u002Fp>\u003C\u002Fth>\u003Cth colspan=\"1\" rowspan=\"1\">\u003Cp>Multiplier 1 (DCA)\u003C\u002Fp>\u003C\u002Fth>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Rung sizes\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>1, 2, 4, 8, 16, 32, 64, 128\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>1, 1, 1, 1, 1, 1, 1, 1\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Total exposure\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>255 × the first order\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>8 × the first order\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Deepest entry\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>93.21\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>93.21\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Average entry\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>94.13\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>96.57\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Take-profit\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>94.60\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>97.05\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>Bounce needed from the deepest rung\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>+1.5%\u003C\u002Fp>\u003C\u002Ftd>\u003Ctd colspan=\"1\" rowspan=\"1\">\u003Cp>+4.1%\u003C\u002Fp>\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003Cp>Read the last two rows together. Doubling pulls the average entry down to within a point of the deepest rung, so a 1.5% bounce closes the ladder in profit. Equal sizing leaves the average three points higher, so the bounce has to be 4.1%, nearly three times as far.\u003C\u002Fp>\u003Cp>Now read the second row. The doubling ladder bought that easier exit with 255 units of exposure against 8. If the first order was 1% of your balance, the doubling ladder at depth eight holds 255% of the balance in position value, and every further 1% drop costs about 2.5% of the balance. The DCA ladder holds 8% and loses about 0.08% per further 1% drop.\u003C\u002Fp>\u003Cp>Martingale isn't a cleverer DCA. It's a bet that price bounces 1.5% before it falls another few percent, made with everything you have.\u003C\u002Fp>\u003Cfigure>\u003Cimg src=\"\u002Fmedia\u002F462c0e4e-0290-4da9-8087-9673e9372a23-e8fd42e2.webp\" alt=\"Dca Vs Martingale Ladder Exposure\" loading=\"lazy\">\u003Cfigcaption>Same eight entries, same prices. Doubling pulls the take-profit down to 94.60, just above the deepest rung; equal sizing leaves it at 97.05, at a cost of 255× the first order against 8×.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\u003Ch2 id=\"section-2\">What you set, and what each setting does to the maths\u003C\u002Fh2>\u003Cp>On a Vectorhelm Martingale strategy the ladder is defined by a short list, and each item changes the table above.\u003C\u002Fp>\u003Cul>\u003Cli>\u003Cp>\u003Cstrong>Direction.\u003C\u002Fstrong> Long or short. A hedging account can run one of each on the same symbol, as two strategies.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>First order size.\u003C\u002Fstrong> A fixed amount or a percent of balance. Everything scales from this.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Multiplier.\u003C\u002Fstrong> Each rung is the previous one times this. 1 is DCA. 2 is doubling. 1.5 is between: eight rungs total about 49 times the first order, with the average entry and the bounce landing between the two columns above.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Price step.\u003C\u002Fstrong> The minimum distance between entries, in percent. Wider steps mean a deeper ladder covers more price for the same number of rungs, and a larger loss at the bottom.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Max steps.\u003C\u002Fstrong> The number of rungs. This is where the exposure is decided. Doubling to eight rungs is 255×; to ten it's 1,023×.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Take-profit.\u003C\u002Fstrong> Percent above the ladder's average entry, shared by every rung.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>What starts the ladder.\u003C\u002Fstrong> A TradingView alert, builder conditions, or always.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>Cooldown.\u003C\u002Fstrong> An optional pause before a new ladder can start after one closes.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cstrong>When a risk limit fires.\u003C\u002Fstrong> Keep the open ladder with its take-profit, or close it.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>Three of those settings decide the exposure between them: first order size, multiplier and max steps. Vectorhelm doesn't work the ladder out for you, so do it before you launch, the way the table above does. Multiply the first order by the multiplier for each rung, add them up, and ask whether you'd hold that total at the deepest entry. If you wouldn't, lower max steps or the multiplier until you would. \u003Ca href=\"https:\u002F\u002Fwww.notion.so\u002Fplatform\u002Fexecution-modes\u002F\">Execution modes\u003C\u002Fa> covers how the four modes differ.\u003C\u002Fp>\u003Cfigure>\u003Cimg src=\"\u002Fmedia\u002F5f48d3e3-3596-4cfa-bf4b-7a37f736e87f-8ed1b335.webp\" alt=\"Vectorhelm Martingale Strategy Settings\" loading=\"lazy\">\u003Cfigcaption>The three settings that decide exposure: first order size, multiplier and max steps. Everything in the table above follows from these.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\u003Ch2 id=\"section-3\">What the next alert does while a ladder is open\u003C\u002Fh2>\u003Cp>A Martingale strategy takes open signals in its direction, and nothing else. There's no close signal for a ladder; it closes at its take-profit.\u003C\u002Fp>\u003Cp>An open signal while the ladder is already open adds a rung, but only if price has moved at least the step distance from the last entry. If it hasn't, the signal is recorded and skipped. That's what stops a script alerting on every bar from stacking five positions at the same price. Above max steps, the signal is refused and the refusal is logged with that reason.\u003C\u002Fp>\u003Cp>If you close one rung by hand, the ladder carries on with the rest, and the take-profit is recomputed from the remaining average.\u003C\u002Fp>\u003Ch2 id=\"section-4\">The limit that actually stops a ladder\u003C\u002Fh2>\u003Cp>This is the part that catches people, and it's worth being precise.\u003C\u002Fp>\u003Cp>A daily loss limit counts closed trades. A ladder that's eight rungs deep and 15% underwater has closed nothing, so the daily loss limit sees nothing. It will not fire. The same is true of any tool that measures loss on realized P&L only.\u003C\u002Fp>\u003Cp>The limit that sees an open ladder is \u003Cstrong>max drawdown\u003C\u002Fstrong>, measured from peak equity, because equity includes the floating loss. Set at the strategy level, it stops that ladder at the depth you chose. Set at the account level, it stops everything on the account, which is the right call when the ladder is one of several strategies sharing a balance.\u003C\u002Fp>\u003Cp>Depth is also capped twice: by the ladder's own max steps, and by the strategy's max open positions limit. The lower one wins. A ladder with max steps at ten and max open positions at six stops at six.\u003C\u002Fp>\u003Cp>So the honest configuration for a Martingale strategy is three numbers, not one. Max steps sets how deep it can go. Max drawdown sets how much it can lose on the way, floating loss included. And the account's max drawdown sits above both, in case the ladder isn't the only thing having a bad day. The ladder has no stop-loss of its own. The limits are the stop.\u003C\u002Fp>\u003Cfigure>\u003Cimg src=\"\u002Fmedia\u002F0b4e11ef-d51b-4165-959a-53c217f9b38f-b2f5a7c9.webp\" alt=\"Vectorhelm Strategy Risk Limits Max Drawdown\">\u003Cfigcaption>Max drawdown is the limit that sees an open ladder. Daily loss counts closed trades only and never fires on a ladder that’s still underwater.\u003C\u002Ffigcaption>\u003C\u002Ffigure>\u003Ch2 id=\"section-5\">The honest limitation\u003C\u002Fh2>\u003Cp>A ladder with a stop is a strategy with a stop. The appeal of Martingale is that it never takes the loss, and a max drawdown limit takes it for you, at the depth you set, on a day that might have bounced.\u003C\u002Fp>\u003Cp>That's the trade. Without the limit, the ladder's loss is bounded only by the account, and the table above shows how fast that bound arrives at eight rungs doubling. With the limit, some ladders get closed that would have recovered. There's no setting that gives you the recovery without the risk, and any tool suggesting there is has left a row out of its table.\u003C\u002Fp>\u003Cp>On a funded account, the arithmetic is worse than it looks here, because the firm's drawdown rule is measured on equity too. A doubling ladder that's 5% underwater on a 10% max drawdown rule has used half the account's life on one trade idea. Most firms also name martingale specifically in their rules, so read yours before the first ladder opens.\u003C\u002Fp>\u003Ch2 id=\"section-6\">Before you run one\u003C\u002Fh2>\u003Cp>Work out the total exposure at max steps for your first order size and multiplier, and decide whether you'd hold that position at the deepest entry. If not, lower max steps or the multiplier until you would.\u003C\u002Fp>\u003Cp>Set max drawdown on the strategy. Then set it on the account.\u003C\u002Fp>\u003Cp>Run it on demo through at least one losing stretch, not just the bounce.\u003C\u002Fp>\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.notion.so\u002Fearly-access\u002F\">Join the waitlist\u003C\u002Fa>. It's free, needs no card, and your invitation comes with a \u003Ca href=\"https:\u002F\u002Fwww.notion.so\u002Fplatform\u002Fdemo-accounts\u002F\">demo account\u003C\u002Fa> running the full risk engine. Build a ladder from a TradingView alert, set the drawdown limit, and watch it close the ladder before it closes the account.\u003C\u002Fp>\u003Chr>\u003Cp>\u003Cem>Vectorhelm is execution software. It runs the rules you define on accounts you own and control. Nothing here is trading advice. Martingale and DCA ladders can lose more than the first order many times over, and no configuration of risk limits prevents losses.\u003C\u002Fem>\u003C\u002Fp>","TradingView DCA Bot vs Martingale: The Real Numbers","Run a TradingView alert as a DCA or Martingale ladder. The exposure at eight rungs, the bounce each needs to exit, and the one limit that stops a ladder.",[151,153,155,157,159,161,162],{"id":50,"text":152},"What a ladder actually is",{"id":53,"text":154},"One setting, two strategies",{"id":56,"text":156},"What you set, and what each setting does to the maths",{"id":59,"text":158},"What the next alert does while a ladder is open",{"id":62,"text":160},"The limit that actually stops a ladder",{"id":65,"text":75},{"id":68,"text":163},"Before you run one",37,{"categories":166},[167,168,169,170,171,172,173],{"slug":6,"sort":7,"name":8,"description":9,"metaTitle":9,"metaDescription":9,"articles":10},{"slug":12,"sort":10,"name":13,"description":9,"metaTitle":9,"metaDescription":9,"articles":14},{"slug":16,"sort":17,"name":18,"description":9,"metaTitle":9,"metaDescription":9,"articles":10},{"slug":20,"sort":21,"name":22,"description":9,"metaTitle":9,"metaDescription":9,"articles":17},{"slug":24,"sort":14,"name":25,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},{"slug":27,"sort":28,"name":29,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},{"slug":31,"sort":32,"name":33,"description":9,"metaTitle":9,"metaDescription":9,"articles":7},1792269977523]