When to Pause Automated Trading, and What Each Control Does

Pause automated trading when the evidence meets an intervention rule you wrote in advance, then verify what happened to open positions. Stopping alerts, halting an EA and requesting a close are different actions. Choose the control by its effect on entries, exits and existing exposure.

Automation executes rules; it does not create a trading edge. Monitoring checks whether the intended rules are still being applied, and whether the assumptions behind them still deserve review. It cannot tell you that a strategy will recover.

Part 8 of 8 in From discretionary to automated trading. Previous: Verify the demo path. Next: Back to the series guide.

What should monitoring answer?

1. Is the path available? Check active alerts, the receiving connection, the terminal and the broker connection. An active alert or connected terminal alone does not establish that a trade occurred.
2. Did the intended request reach the intended account? Reconcile TradingView's alert log, Portal's Bridge / Signals log, and MT5 Experts/Journal with the broker's orders, deals and positions. A processing status is not a substitute for the broker outcome.^[1]
3. Does the observed behaviour still fit the specification? Separate operational defects from expected fill differences and from evidence that a strategy assumption needs fresh validation. Return to Part 6 for the research question.

On PineConnector Edge, hosted MT5 Experts and Journal logs are available in Portal → Edge. The Edge page and the dated 17 September update establish that access. Connection monitoring does not remove the need to inspect broker exposure.^[2][3]

How often should you check?

Choose check times that fit your strategy's holding period and the time you could leave a fault unresolved. The following is a working schedule to adapt, not a claim that daily or weekly checks are sufficient for every setup.

• At an error or disconnect notice: identify the account, signal and broker outcome before deciding whether another request is needed. Plus and Pro include Signal Error and Connection Lost tasks, with email and Telegram. A notice does not repair or resend a signal.^[4]
• At your chosen session checks: verify alert status and expiry, connection state, current positions, pending orders and protection. Reconcile new signals with the Part 7 worksheet. Core includes Close All Trades and Trading Time Limit with email, but not the two Premium notification tasks, so specify your direct checks.^[4]
• At the planned review interval: compare actual activity with the written rules and the conditions you tested. Check notification schedules, saved alert versions and Analytics freshness. Analytics refreshes on demand and stops updating if the EA or account disconnects; it is not documented as a realtime drawdown alarm.^[5]
• After a script, input, routing or EA change: review the affected configuration and repeat the relevant demo acceptance cases. TradingView alerts retain a saved script/input snapshot; editing the chart does not update the existing alert.^[6]

The Tasks guide requires MT5 EA v3.45 or later. Check Edge task controls in Portal or with Support; an eligible plan does not prove that a particular hosted control is available. Turning off a task's notification delivery does not disable its trading action.^[4]

What does each off-switch do?

The twelve control cards below are a compact reference. “Requests closure” does not mean “positions are closed.” Check every affected broker account. “Not documented” means the cited source does not settle that behaviour; it does not prove support or lack of support.

1. Stop a TradingView alert.
   Entries and exits: that alert stops triggering, so both stop if it carries both. Separate alerts are unaffected. Open positions: no close is requested. Scope and resume: the selected alert; resume it only after checking state, expiry and the saved version. Availability is through TradingView's alert controls.^[7]
2. TradingView notification schedule.
   Entries and exits: webhook notifications outside the schedule are suppressed, including exit webhooks. Open positions: no close is requested. Scope and resume: the scheduled alert notifications; restore the required delivery window and verify exits separately. Keep notification delivery available throughout the day when the trading design needs it.^[8]
3. eaoff / eaon.
   Entries and exits: eaoff requests a halt to incoming signal processing. No exit exemption or later replay is documented. Open positions: no closure is requested. Scope and resume: no per-comment scope is documented; examine every account connected to the License ID. eaon requests resumption. Verify the received state and version; Edge support for these controls is not established by the cited pages.^[9]
4. closealleaoff.
   Entries and exits: requests closure/cancellation within scope, then a halt. Open positions: verify which closure requests completed; remaining positions still need attention. Scope and resume: the receiving EA's scope across symbols, not only the third-field chart symbol. Inspect scope and broker results before requesting resumption. Do not infer comment isolation or Edge availability.^[9]
5. closeall.
   Entries and exits: does not request a signal-processing halt. Later entries remain possible. Open positions: requests closure and pending-order cancellation within scope. Scope and resume: the EA's scope across symbols; the chart-symbol field is not a symbol-only filter. There is no halt to resume from this command itself. Verify its applicability on the receiving version.^[9]
6. Portal Trading Time Limit.
   Entries and exits: signals are halted outside the window; an exit exemption and queued-signal behaviour are not documented. Open positions: no scheduled close. Scope and resume: inspect the task's accounts and tile timezone. Adjust the window or task state, then check its saved configuration. Core, Plus and Pro include this task; Edge availability needs confirmation.^[4]
7. Portal Close All Trades.
   Entries and exits: performs a scheduled closing action; do not treat it as an entry halt. Open positions: requests closing market positions and removing pending orders at the configured weekly time. Scope and resume: verify task accounts and position scope; do not assume one comment. Edit or disable the task to change the future action. Core, Plus and Pro include it; confirm hosted availability.^[4]
8. EA Start Time / End Time.
   Entries and exits: signals outside Active hours are ignored; an exit exemption is not documented. Open positions: no closure is requested by the window. Scope and resume: receiving EA, using broker-server time. Check the next window or amend self-hosted inputs on demo. Edge's EA inputs are fixed and cannot currently be edited.^[10][2]
9. EA Daily / Cumulative protection.
   Entries and exits: depends on the configured action. Halt, Close All and Close and Halt have different effects. Open positions: only a closing action requests closure. Scope and resume: verify account calculation, position scope and reset boundary. A day halt and a persistent halt resume differently; persistent halts require manual resumption. These are self-hosted settings, not editable Edge inputs.^[10]
10. MT5 Algo Trading / AutoTrading off.
    Entries and exits: prohibits automated trading by EAs in that terminal, including automated closes; EA calculation may continue. Open positions: no closure is requested. Scope and resume: all EAs in that terminal, not just one strategy. Re-enable the toolbar and required EA permission after checking broker state. This is a terminal control, not an exposed Edge desktop button.^[11]
11. Restart or terminate Edge.
    Entries and exits: a stopped hosted terminal cannot send EA trading requests while stopped. Open positions: stopping it does not close them. Scope and resume: the selected hosted instance; restart and terminate are different lifecycle actions. Inspect the resulting instance and connection state, then recheck routing and exposure before enabling alerts. A restart is not an exit procedure.^[2][12]
12. Cancel the subscription.
    Entries and exits: cancellation is a billing action, not a precise timed trading switch. Check service status and effective dates separately. Open positions: cancellation does not close them. Scope and resume: the subscription and its service allowance; do not assume reactivation restores previous alerts or reconciles positions. Manage broker exposure directly.^[12]

Broker-side SL/TP is separate. MetaTrader describes accepted SL/TP as server-side protection, while its trailing stop runs in the trading platform. A terminal shutdown does not remove already accepted broker SL/TP, but a stop price is not a promise of the execution price. Check what protection is actually recorded.^[13]

EA-managed Shadow Targets, breakeven or trailing adjustments require their own availability check. The cited PineConnector pages do not establish their behaviour during each halt state. Do not assume these controls continue while the terminal is off, or confuse them with accepted broker SL/TP.^[10]

How do you write an intervention rule?

Complete one worksheet row for each trigger class. Supply your own thresholds and review intervals; this guide recommends no loss limit, holding time or market response.

1. Trigger: technical fault, execution mismatch, account-limit event, broken strategy assumption, scheduled event or discretionary concern: ______.
2. Evidence: exact observation and timestamp: ______. Account and signal reference: ______. Threshold, units, observation window and reset timezone: ______.
3. Action: investigate, restrict new entries, request closure, halt, or return to research: ______. Selected control from the twelve cards: ______.
4. Exposure: affected accounts, positions and pending orders: ______. Exit route that remains available: ______. Responsible person and escalation route: ______.
5. Resume test: what must be corrected and independently observed: ______. Evidence location and review time: ______. If unknown, remain in the chosen protective state and investigate.

Illustrative example, not a recommendation: the London pullback's 16:00 close request appears in the alert log, but the broker position remains open at the trader's chosen follow-up check. Record it as an unresolved exit. Investigate delivery, processing and broker outcome before another request. A zero Pine simulated position would not settle it.

A concern about drawdown belongs in a different row from a lost connection. A simulated strategy limit, an EA account limit and a broker or firm's rule can use different equity definitions and reset clocks. State the calculation you intend and check logged values; a similarly named setting does not establish equivalence.^[10]

What must be true before you resume?

• Cause resolved? Record the correction or research decision. Clearing a halt without resolving its trigger is incomplete.
• Every recipient accounted for? Check the License ID's connected accounts, actual positions and pending orders. Match comments only where the exact command documents that filter; do not infer partial-close or account-wide isolation.^[9]
• Simulated and broker states reconciled? Explain each difference. Do not force them to agree by resending an entry or exit with an unknown prior outcome.
• Exit path available? Check alerts, notification schedule, processing windows, permissions, broker hours and accepted protection. An entry-only restriction can preserve a separate exit path only if the downstream controls allow it.
• Configuration current? Inspect the saved alert version, routing and receiving EA configuration. Remove duplicate alert or EA sources before resuming.
• Affected demo cases passed? Repeat the relevant Part 7 checks after a material change. A connection test alone does not establish a broker trade. Document who will monitor the resumed path.

If an answer is no or unknown, keep the chosen restriction in place while you investigate and manage open exposure through the verified broker route. Do not send continuous connection tests as a substitute for monitoring.

What are the limits of these controls?

No trading account, halt, restart or resume procedure was tested for this guide. Behaviour can depend on the EA build, account mode and hosted controls. Exit exemptions, queued signals, Edge command availability and some action scopes remain undocumented in the captured sources. Ask Support about the exact version and verify on demo before relying on them.

Monitoring detects evidence to act on; it does not establish that every fault will be observed before exposure changes.

What is the next step?

Fill the intervention worksheet and attach it to your strategy specification. Use the series guide to return to readiness, backtesting or demo verification when the evidence calls for a change.

Reviewed 23 September 2026 against primary documentation captured on that date. Nothing was tested on a trading account, and no Pine Script or MQL5 code was compiled.

Related reading

• From discretionary to automated trading
• Verify the demo path
• Write rules and choose their enforcement layer
• Notification schedules and webhook delivery

Sources

1. PineConnector – Recommendations, accessed 23 September 2026.
2. PineConnector – Edge, accessed 23 September 2026.
3. PineConnector – Updates, 17 September 2026, accessed 23 September 2026.
4. PineConnector – Tasks, accessed 23 September 2026.
5. PineConnector – Analytics, accessed 23 September 2026.
6. TradingView – Alerts FAQ, accessed 23 September 2026.
7. TradingView – Manage alerts, accessed 23 September 2026.
8. TradingView – Notification schedule for alerts, accessed 23 September 2026.
9. PineConnector – Syntax, accessed 23 September 2026.
10. PineConnector – EA settings, accessed 23 September 2026.
11. MetaQuotes – Platform Settings, accessed 23 September 2026.
12. PineConnector – FAQ, accessed 23 September 2026.
13. MetaQuotes – Orders, deals, positions and protective orders, accessed 23 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.