Semi-automated trading is a setup in which software carries out some trading decisions and a person keeps the rest. Three common forms are TradingView alerts that notify you while you place or skip each trade, manual entries with automated exits, and automated entries with a logged human veto. PineConnector's published docs, as of 25 September 2026, describe no step that holds an incoming alert for your approval.
Choosing a hybrid is a decision about who acts at each stage, not about whether the strategy works. Automation executes the rules you supply; it does not create a trading edge. The series guide to getting started with automated trading sets out the stages in order.
Semi-automated trading at a glance
Scroll horizontally to read every column.
| Setup | What a person does | What automation does |
|---|---|---|
| Alerts, manual orders | Reads each notification, decides, and places or skips the order in MT5 | TradingView evaluates the condition and sends a notification; nothing reaches the broker automatically |
| Manual entries, automated exits | Opens the position | A broker-side stop and target, or later messages that request stop changes or closes |
| Automated entries, logged veto | Pauses, resumes or overrides, and records why | TradingView alerts reach PineConnector and are processed under the EA's settings |
Each row keeps the execution stages separate: the condition becoming true, the alert triggering, webhook delivery, PineConnector processing, the EA's order request, and broker acceptance and fill. The human step sits at a different stage in each row.
Does PineConnector offer a manual approval step for alerts?
Not in the docs reviewed for this page. The captured PineConnector docs describe entry filters, EA settings, pause commands and Portal Tasks. None describes a queue that holds a signal until you confirm it. If you need per-trade confirmation, ask PineConnector whether it exists before designing around it.
Telegram is documented as a delivery channel for PineConnector Tasks notifications, not as an approval tool.[1] The notification tasks are Signal Error and Connection Lost. The Tasks guide says a Signal Error notification “reports the problem; it does not correct or resend the signal.”[2]
“Alerts with manual approval” therefore means one of two things in a TradingView-to-MT5 workflow. Either the alert notifies you and never reaches PineConnector, or automation runs and you keep documented controls to pause it.
How do alerts with manual orders work?
A TradingView alert can notify you without a webhook. TradingView lists push, email, sound, webhook, toast and desktop app push among its alert channels.[3] If no webhook is set, no message reaches PineConnector. You read the notification, check the chart and your broker quote, and place the order in MetaTrader 5 yourself.
- Keeps: a per-trade judgement, including the discretionary checks you have not yet written as rules.
- Loses: consistent timing. The order waits for you to see the notification, and your fill uses the broker's price at that later moment.
- Silent gaps: an alert can fire without a notification, depending on its settings.[4] Outside a notification schedule, every channel, including webhooks, is blocked.[3]
Log three times for each signal: the alert trigger, your decision, and the broker's execution. Without that record, you cannot tell a skipped trade from a missed notification.
Can you enter manually and automate only the exits?
Yes, with limits that depend on which exit mechanism you use. A Stop Loss and Take Profit set at entry are stored and executed on the broker's server, so they do not depend on your terminal running.[5] That is the simplest automated exit for a manual trade.
PineConnector's automatic breakeven and trailing parameters are different. The syntax reference says they “configure later stop changes when opening an entry”, so they belong to an entry message the EA receives.[6] A position you opened by hand did not come from such a message.
Management messages such as newsltplong or closelong reach a manually opened position only when Magic Restriction is Off.[7] The guide to automating exits only covers the exact parameters, their units, and what happens when TradingView and the broker disagree.
How does a logged veto work with automated entries?
Here, entries run automatically and you keep the power to stop them. PineConnector documents these controls, as of 25 September 2026:[6][2]
-
eaoff: halts processing of incoming signals. It does not request position closure. -
eaon: resumes a halted EA. It does not request a new entry. -
closealleaoff: requests closure and cancellation within scope, then a halt. It uses the receiving EA's chart symbol as the third field. - Trading Time Limit task: processes signals inside a configured window and halts them outside it. It is not a scheduled close. The Tasks guide requires PineConnector MT5 EA v3.45 or later.
Illustrative messages, not instructions to trade. Each goes in the Message field of a TradingView alert that uses the PineConnector webhook. Verify each control on a demo account first, and check how your version records a halted signal.
LicenseID,eaoff,eaoff
LicenseID,eaon,eaonA veto is only useful if it is logged. Record the time, the reason, the control used, the EA's state afterwards and any open positions it left in place. The guide to pausing automated trading compares what each off-switch actually does.
How do you stop manual and automated trades colliding on one account?
Two settings decide the outcome: the EA's Magic Restriction and the account's position accounting system.
-
Magic Restriction On, the documented default, limits management to positions whose magic number matches the EA. With it Off, closing commands, Pyramiding, Close on Reverse, position counts and SL/TP modifications can include manual positions. The docs give the example that
closelongwith restriction off “can affect manual buy positions”.[7] - Maximum Open Positions per Symbol controls new signals from the EA. It “does not prevent a manual order or another EA from opening a position.”[7]
- Netting accounts hold one position per symbol, so a manual order and an automated order on the same symbol change one shared position. Hedging accounts open a new position for each fill.[8]
Illustrative netting example. An automated 0.50-lot EURUSD buy is open with a Stop Loss. You then buy 0.20 lot by hand from the order window and clear its Stop Loss field. The account now holds one 0.50 + 0.20 = 0.70-lot buy. MetaQuotes' netting rule places the Stop Loss and Take Profit “according to its latest order” when volume increases. If the new order specifies zero values, the position's levels are deleted.[8] Your manual order has removed the automated stop.
MetaQuotes adds two safeguards. The order window pre-fills the position's current levels “to prevent accidental deletion”, and one-click trading leaves them unchanged.[8] The stop disappears only when the manual order carries zero levels.
The sources used here do not say which magic number such a merged position then carries. Test that on demo before sharing a netting account between manual and automated trading. The guide to manual, systematic and automated trading explains the Magic Restriction trap in more detail, and the netting vs hedging guide works through the account rules.
Illustrative workflow: setting up a hybrid on a demo account
- Split the decisions. List each decision in the strategy and mark it automate, test first, or keep with a logged veto. The strategy readiness checklist gives that inventory.
- Choose the setup for each part. For example: automated entries, broker-side stops set by the entry message, and a manual veto for scheduled events.
- Check the account. Confirm netting or hedging, Magic Restriction, and every account connected to the License ID.
- Test the automated path. Send one demo entry and compare the resulting order, position, stop and target with your intention.
-
Test the veto. Send
eaoff, trigger a demo entry alert, and check the Signal Log and Experts log for how the halted signal is recorded. Sendeaonand confirm the state. - Test a manual trade beside it. Place a demo trade by hand and send a close command. Confirm which positions were affected.
What semi-automation does not solve
- No added edge. A person approving trades does not show the rules have positive expectancy.
- Human steps are slower and less consistent. Backtest results assume the rule acts at the signal; a manual step changes when, and whether, it acts.
-
A halt is not a close.
eaoffleaves existing positions and their broker-side stops in place.[6] - Per-trade approval is undocumented. Do not assume a confirmation step exists in PineConnector; confirm with the vendor.
Frequently asked questions
What is semi-automated trading?
Semi-automated trading splits a strategy between software and a person. Common forms are TradingView alerts that notify a trader who places orders by hand, manual entries with automated exits such as broker-side stops, and automated entries that a trader can pause or override. Each form keeps the human step at a different stage of execution.
Can I approve TradingView alerts before PineConnector places a trade?
PineConnector's published docs, as of 25 September 2026, describe no approval step for incoming alerts. Telegram is documented for Tasks notifications such as Signal Error and Connection Lost. To approve each trade yourself, send the TradingView alert to a notification channel instead of the webhook, then place the order manually.
Can I trade manually on the same account as an automated strategy?
You can, but test the interaction first. With PineConnector's Magic Restriction Off, close and modify commands can affect manual positions. On an MT5 netting account, a manual order on the same symbol merges with the automated position, and its stop levels can replace the existing ones. A separate demo check shows the actual result.
Is semi-automated trading safer than automating everything?
There is no general answer. A human step can catch conditions the rules do not describe, but it also adds delay, missed notifications and inconsistent decisions. Neither approach establishes that a strategy has positive expectancy. Compare the specific risks, such as unattended failures or late manual fills, for your own setup.
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
- How to get started with automated trading: the series guide
- Automate exits only: stops, breakeven and trailing
- Discretionary, systematic or automated trading
- When to pause automated trading
- Netting vs hedging accounts in MT5
Sources
- PineConnector – Telegram notifications, accessed 25 September 2026.
- PineConnector – Tasks and notifications, accessed 25 September 2026.
- TradingView – Notification schedule for alerts, accessed 25 September 2026.
- TradingView – Pine Script FAQ: Alerts, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Executing Trades, accessed 25 September 2026.
- PineConnector – PineConnector Syntax: breakeven, trailing and EA controls, accessed 25 September 2026.
- PineConnector – EA settings reference: Magic Restriction and position limits, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Basic Principles, 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.
