Infrastructure, Cloud & Performance
VPS/cloud architecture, cBots/Open API, latency, reconnects, testing and operations.
Not necessarily. cTrader supports 24/7 cloud cBot execution without a user-managed VPS, but cloud cBots have technical restrictions such as no HTTP requests and WebSocketClient…
037How do I measure TradingView-to-cTrader latency correctly?Timestamp the signal/alert, webhook receipt, connector dispatch, cTrader request, acknowledgement and broker fill. Report median and tail latency rather than one best-case number.
038Connector latency vs broker execution latency: what is the difference?Connector latency covers receiving, validating and forwarding the signal; broker execution latency occurs after the trading request reaches the execution side. Measure them…
039cTrader Open API vs cBot: which is better for a TradingView bridge?Open API lets an external application access cTrader accounts and trading operations; a cBot runs inside cTrader Algo. Authentication, hosting, cloud restrictions and operational…
047What are cTrader Cloud limitations for HTTP and WebSocket connections?cTrader Cloud runs cBots in Linux. Official documentation says HTTP requests are not sent in Cloud and WebSocketClient works only through port 25345; Windows-only dependencies…
048Local PC vs VPS vs cTrader Cloud vs managed connector: which architecture should I use?Choose among local PC, VPS, cTrader Cloud and a managed connector based on uptime, maintenance, integration needs and technical restrictions. They solve different parts of the…
049How do I test TradingView-to-cTrader automation safely before going live?Use a cTrader demo account and deliberately test success and failure paths: entries, exits, duplicate delivery, malformed messages, symbol mapping, closed markets, disconnects,…
050How should an automated trading audit log be designed?An audit log should reconstruct one signal from TradingView trigger to final broker result: signal ID, timestamps, normalized command, target account/symbol, validation,…
060Why does my backtest entry price differ from my live cTrader entry?Backtests use TradingView's broker emulator and historical bar data; live cTrader orders encounter real bid/ask prices, spread, latency, slippage, market hours and broker…
061What is slippage in automated trading?Slippage is the difference between the expected/reference execution price and the price actually obtained. It can be positive or negative and becomes especially important for…
064Which cTrader errors should automated trading retry automatically?Retry only errors that are plausibly transient and only under a bounded, duplicate-safe policy. Connectivity or temporary service failures may justify a retry; invalid volume,…
065Which cTrader errors should never be blindly retried?Do not blindly resend deterministic rejections such as BadVolume, UnknownSymbol or InvalidStopLossTakeProfit. Repeating an unchanged invalid request adds load and can create…
066How should reconnect logic work when cTrader disconnects?Reconnect logic should detect the disconnect, stop unsafe dispatch, restore authentication/session state, reconcile open orders and positions, and only then resume new commands.…
097How should NRUNO handle maintenance without losing or duplicating signals?Maintenance needs a defined intake/execution policy: drain or pause, durably persist accepted commands, stop at a safe boundary, reconcile after restart and keep retries…
098What should an automated trading status page show?A status page should separate public service health from private account state. Publicly show webhook/routing/platform incidents; privately show a user's cTrader connection and…
099How should users be notified when an automated trade fails?Failure notifications should be actionable: signal ID, symbol, account alias, stage, exact error, timestamp and next check. Avoid noise for intentionally ignored duplicates or…