Two connection paths: local ZeroMQ or MetaAPI cloud
Either path is write-capable. Investor-password journal bridges (the pattern in some competing MT5 journals) cannot flatten. If the goal is prop protection, a read-only connection is a dashboard, not a guard.
Retcode 10016, STOPLEVEL, and why gold rejects an 8-point stop
FundedNext also counts 200 executed trades per day. A scalper who splits every idea into 8 micro tickets can fail the trade cap while still looking quiet on the request cap. Count both. Apex and Topstep are not MT5 desks; their message limits are CME ratios on Rithmic, Tradovate, or TopstepX, and they live on the futures pages, not in this ZeroMQ hub.
Mobile fills, Telegram /close, and the PC that went to sleep
Presets are scalp, intraday, and swing. They change pip distances, not the socket. Asset-aware pip values (gold $100/point, EURUSD $10/pip, NAS100 $1/point) live in the same guard so a 20-pip template is not dropped onto XAUUSD.
Install the bridge, then set the flatten line
start free on Venasri and open 24/7 MT5 Bot Control only after the bridge is green. The 2,000-request budget is a trailing-step problem (price steps, not tick steps). This hub's remaining pages are the retcode cookbook and the VPS latency notes for that budget.