The first month of automated trading is a verification period, not a performance test. Run the TradingView, PineConnector and MetaTrader 5 setup on a demo account first. Reconcile every alert with its processing record and broker outcome, compare fills and costs with the backtest's assumptions, and write your pause triggers before day one. Move to a live account, or change size, only when rules you wrote in advance are met.
This checklist follows the first verified demo trade in From discretionary to automated trading. Nothing here judges the strategy by profit. Thirty days rarely hold enough trades for that, and a successful demo order verifies the setup, not the strategy.[1]
The first 30 days at a glance
Scroll horizontally to read every column.
| Stage | Focus | Done when |
|---|---|---|
| Before day 1 | Written plan version, recipients, symbols, units, pause triggers | Every item on the pre-flight list has an answer |
| Days 1–7, demo | Reconcile every signal across three logs | Each alert matches one processing record and one expected broker result |
| Days 8–14, demo | Compare with the backtest; exercise edge cases | Differences are explained and recorded |
| Days 15–30 | Live only if the written go-live rules pass; otherwise keep testing on demo | Daily reconciliation continues with no unexplained mismatch |
The day ranges show a typical order of work, not a schedule to hit. If a stage is not done, stay in it.
Before day 1: what must be written down?
- The plan version. Freeze the rule set and alert settings you are testing. A running TradingView alert uses the script and inputs saved when it was created, so recreate alerts after any change.[2]
- Every receiving account. An alert addressed to a License ID goes to every account connected to that ID, not only the one you are viewing in Portal.[3] Confirm that all of them are demo accounts.
- The exact broker symbol. The symbol field must match the broker's name, including suffix and letter case.[4]
-
Explicit units. PineConnector's docs recommend explicit-unit parameters such as
vol_lots=andsl_pips=for new messages.[4] Size is your decision; this page recommends none. - Where MT5 runs. TradingView runs alerts on its servers. On a self-hosted setup, the MetaTrader terminal and PineConnector EA must stay running and connected on your computer or VPS.[5] If you would rather run your own terminal on a server, ForexVPS (affiliate link) offers Windows VPS plans for MetaTrader. On PineConnector Edge, MT5 and the PineConnector EA are hosted, so no terminal runs on your own computer.[3]
- Pause triggers and owner. Write what stops new entries, who acts and what happens to open positions. See when to pause automated trading.
- A journal. Set up the trading journal fields for alert, processing and broker records before the first signal.
Days 1–7: how do you reconcile every signal?
Keep the stages separate. The alert condition becomes true and the alert triggers. The webhook is delivered, which is a separate event from the notification.[6] PineConnector processes the message. The EA sends an order request, and the broker accepts or rejects it. A fill produces a deal and a position.
Check three logs in this order, as the PineConnector docs describe:[7]
- TradingView Alerts log: did the condition trigger, and what message was sent?
- PineConnector Signals log: was the message received, and how was it processed? A received signal is not, by itself, proof of a broker fill.[8]
- MetaTrader Experts and order history: what did the terminal and broker do? On Edge, the hosted terminal's Experts and Journal logs are in Portal.[3]
Log each signal as matched, mismatched or unexplained. The documented readiness test is that the intended alert matched its processing record and the expected broker trade, with no unintended duplicate.[1] Before retrying anything, check the account for an existing order.
Reconciliation rate = alerts matched to one processing record and one expected broker result / alerts triggered
Start with the documented connection test and one demo order. The connection test sends a fixed test message and does not verify a broker trade.[9] For the demo order, first confirm that every account on the License ID is a demo account. The docs' demo message goes in the TradingView alert's Message field, and the webhook URL goes under Notifications:[9]
LicenseID,buy,EURUSD,vol_lots=0.01Illustrative message from the PineConnector test guide, for a demo account only. It requests a buy of 0.01 lots, with no stop or target. Replace the License ID and use your broker's exact symbol and a permitted volume. Choose your own symbol, size and rules; the example is not an instruction to place a live trade.
Days 8–14: how do live fills compare with the backtest?
A chart marker, a simulated strategy fill and a broker trade are different events.[7] Compare each item below between the backtest's assumptions and the demo record for the same period.
| Item | Backtest side | Demo or live side |
|---|---|---|
| Signal count | Strategy Tester trades in the period | Alerts triggered and matched |
| Fill timing | Broker emulator, often next bar's open[10] | MT5 deal time, in server time |
| Slippage | A fixed setting in the strategy properties | Fill price versus alert price, per trade, signed by direction |
| Costs | Commission as modelled | Broker commission, spread and swap |
| Exits | Simulated stops and targets | Broker-side SL/TP or separate close requests |
TradingView describes slippage as dynamic and unpredictable, and impossible to simulate precisely; a fixed setting is an approximation.[11] TradingView and MetaTrader can also differ in data feed, quotes, spread and timestamps.[5] Record the differences in pips and in R. See slippage and why TradingView and MT5 results differ.
Use this week to exercise the cases your rules must handle: a fresh entry, an opposite signal and a repeated same-direction signal. The docs list these checks after any change to Close on Reverse or Pyramiding.[12] Change one thing at a time, and keep the previous working version.
Days 15–30: when is going live justified?
Write the go-live rules before the demo starts, and phrase them as process checks rather than profit. For example:
- a number of consecutive signals, chosen by you, reconciled with no unexplained mismatch;
- every edge case from days 8–14 tested and recorded;
- slippage and cost differences explained and inside the range you wrote down;
- pause triggers, owner and open-position handling written and rehearsed;
- the live account identified, and the full list of accounts on the License ID reviewed again.
If any check fails, stay on demo. After moving to live, keep the same daily three-log reconciliation. On plans that include them, the Signal Error and Connection Lost tasks send notices; a notice does not correct or resend a signal.[13] The task guide requires PineConnector MT5 EA v3.45 or later.
What should trigger a pause in the first month?
Decide the triggers in advance: an unexplained mismatch, a duplicate order, a missing alert, a disconnect, a rule or alert change, or slippage outside your written range. The pause guide covers who acts and how to restart.
Know what each control does. As of 25 September 2026, the EA control commands are documented as follows: eaoff requests a halt to incoming signal processing and does not request position closure, and closealleaoff closes positions and cancels pending orders within scope, then halts.[4] Whether eaoff works on an Edge instance is not documented; confirm with PineConnector Support and test on demo. Cancelling a subscription, or a stopped hosted terminal, does not close broker positions.[5]
When is it reasonable to scale up?
Only when a scaling rule you wrote before the month began says so. A good month's result is not that rule: thirty days usually hold too few trades to separate an edge from chance, as the sample-size guide explains.
Treat any size change as a new version. Broker minimum, maximum and step volumes come from the symbol specification. PineConnector's syntax reference says to check the requested and the accepted volume rather than assume a rounding direction.[4] Verify the first orders at the new size in the Experts log and order history.
What does this checklist not cover?
- Strategy quality: a clean reconciliation shows that the setup behaves as specified. It does not show that the rules have an edge.
- Every broker's rules: sessions, symbol specifications and account types vary by broker. Check your own.
- Uninterrupted service: a VPS or hosted terminal does not establish uninterrupted service.[14] Monitoring still needs an owner.
- Undocumented behaviour: where the docs are silent, test on demo or ask Support rather than assume.
Frequently asked questions
What should you check in the first month of automated trading?
In the first month of automated trading, check that every TradingView alert matches one PineConnector processing record and one expected MT5 broker result, with no duplicates. Compare fill timing, slippage and costs with the backtest's assumptions. Test opposite and repeated signals on demo, and write pause and go-live rules before starting.
How do you go live with automated trading?
Go live only after a demo period in which the rules you wrote in advance pass: a run of reconciled signals, tested edge cases, explained cost and slippage differences, and rehearsed pause steps. Then review every account on the License ID, choose your own size, and keep reconciling each signal daily.
How do you monitor an automated trading system?
Monitor an automated trading system by reading three logs in order: the TradingView Alerts log, the PineConnector Signals log, then MetaTrader's Experts log and order history. Record each signal as matched or not, check open positions directly at the broker, and act on pause triggers written in advance.
How long should you demo test before going live?
No universal period applies. Demo test until the go-live checks you wrote beforehand pass, such as a chosen number of consecutive reconciled signals and every edge case tested. A demo pass verifies the setup. It does not establish that the strategy will be profitable, which needs a much larger sample.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account.
Related reading
- From discretionary to automated trading: the series guide
- From a TradingView backtest to a verified demo trade
- When to pause automated trading
- How to keep a trading journal (fields and template)
Sources
- PineConnector – Test your setup: finish the test, accessed 25 September 2026.
- PineConnector – No-code automation: add the webhook and check the result, accessed 25 September 2026.
- PineConnector – PineConnector Edge, accessed 25 September 2026.
- PineConnector – Syntax reference, accessed 25 September 2026.
- PineConnector – Frequently asked questions, accessed 25 September 2026.
- PineConnector – Missing signals: was the webhook configured and delivered?, accessed 25 September 2026.
- PineConnector – Best practices: compare logs in the right order, accessed 25 September 2026.
- PineConnector – Frequently asked questions: Signals log, accessed 25 September 2026.
- PineConnector – Test your setup, accessed 25 September 2026.
- PineConnector – Low-code automation: check where the entries appear, accessed 25 September 2026.
- TradingView – Strategies, accessed 25 September 2026.
- PineConnector – Best practices: change one thing at a time, accessed 25 September 2026.
- PineConnector – Tasks and notifications, accessed 25 September 2026.
- PineConnector – VPS setup: keep MT5 running, accessed 25 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
