A TradingView alert can now appear in your Alerts log without sending its webhook. Since 7 July 2026, each alert can carry a notification schedule: a set of days and hours when it is allowed to notify you. Outside those hours the alert keeps checking its condition and records every trigger, but TradingView blocks every notification channel, including the webhook.
For an alert that sends instructions to PineConnector, a muted trigger means no message leaves TradingView, so PineConnector has nothing to process and MetaTrader places nothing. TradingView's own advice for automated setups is to keep those alerts on a 24/7 schedule. This article explains how schedules behave, where time zones catch people out, and what to check on every alert that feeds an automated workflow.
What changed
TradingView announced notification schedules on 7 July 2026 (the post was last updated on 7 August 2026)[1]. Before that, an active alert sent its enabled notifications whenever it triggered. Now you can choose, per alert, the days and hours in which it may send push notifications, emails or webhooks.
TradingView's Help Center lists the choices[2]:
- 24/7 (Always Active), the default.
- Weekdays, Monday to Friday, silent on Saturday and Sunday.
- Standard working hours, Monday to Friday from 09:00 to 18:00.
- Custom schedule, with your own days and a From/To window down to the minute. A window such as 22:00 to 04:00 crosses midnight, and entering the same time in both fields (for example 00:00 to 00:00) means the full day.
Two convenience features travel with it. TradingView remembers your last schedule and applies it by default to the next alert you create "if it's applicable", and a schedule can be saved inside an alert preset[2]. Alerts with a schedule show a small calendar icon next to their status in the alert manager.
What a muted trigger looks like at each stage
TradingView's Help Center lists what is blocked outside the schedule: push, email, sound, webhook, toast and desktop app notifications. It also makes clear that the schedule controls delivery, not triggering, so a trigger outside the schedule still appears in your alert log[2]. TradingView describes a muted trigger as recorded, not queued. Neither the announcement nor the Help Center says a muted notification is delivered later.
Read along the chain and each stage tells a different story:
| Where you look | Trigger inside the schedule | Trigger outside the schedule |
|---|---|---|
| TradingView Alerts log | Entry recorded | Entry recorded |
| Webhook sent to PineConnector | Yes, subject to normal delivery | No. The webhook is blocked with every other channel |
| PineConnector Bridge (signal log) | The received message and its processing result | Nothing, because nothing arrived |
| MetaTrader and broker | The EA may send an order; check separately whether the broker accepted it, filled it and left a position open | No new instruction to act on |
The trap is the first row. A log entry proves that TradingView evaluated the condition and triggered. It does not prove that a webhook left TradingView. PineConnector's troubleshooting guide draws the same line: an alert notification and a successful webhook delivery are different events[6].
"Once only" alerts get a second chance
A single-use alert behaves differently from the rest. If a "Once only" alert's condition is met while it is muted, TradingView records the trigger in the alert log but does not deactivate the alert. Once the schedule is active again, the alert waits and notifies you the next time its condition is met[2].
For notifications to your phone, that is helpful. For an entry instruction, it changes which event PineConnector receives. Suppose a "Once only" alert on EURUSD is set to cross above 1.0850, with a schedule of 09:00 to 18:00. Price crosses at 06:40, which is muted and logged. The alert stays armed. If price then crosses above 1.0850 again at 13:05, the webhook goes out at 13:05, at whatever the market is doing then. The first crossing never reached PineConnector. These times and prices are illustrative; the point is that the instruction PineConnector receives belongs to the later event, not the one you saw first.
Which clock is the schedule using?
Three different clocks appear around a TradingView alert, and a schedule set in the wrong one silently shifts your window.
| What you are looking at | Time zone TradingView uses |
|---|---|
| The notification schedule (presets and custom windows) | Your TradingView account time zone. If you change it, the schedule shifts "after restarting the alert"[2] |
| Alert manager and Alerts log | Your operating system's time zone[3] |
| Alerts log CSV export | UTC[3] |
{{time}} and {{timenow}} in a message |
UTC[4] |
| The chart's time zone setting | "doesn't affect alerts in any way"[3] |
A worked example shows how this bites. A trader whose account time zone is Singapore (UTC+8) picks "Standard working hours" for a London-session strategy. The window is 09:00 to 18:00 Singapore time, which is 02:00 to 11:00 in London while British Summer Time applies. Most of the London afternoon falls outside the schedule, and every trigger in it is logged but not sent. Before you compare logs, note which time zone each one displays, and convert to one of them. PineConnector's support checklist asks for the "Alert time and timezone" for the same reason[6].
Can a schedule work as a trading-hours filter?
A schedule controls notifications. It does not know whether a message opens or closes a position, so it mutes both. That makes it a poor substitute for session rules in an automated strategy.
- Silencing phone and email pings for a manual-trading alert overnight: a good fit. TradingView designed schedules for this kind of use.
- Keeping an automated strategy from entering outside a session: risky. Exit alerts on the same schedule are muted as well, so a position opened inside the window can miss its closing instruction, and a "Once only" entry can fire later at a different price.
- Limiting when PineConnector acts on signals: a separate tool. On a self-hosted terminal, the PineConnector EA's Active hours inputs set a window, in the broker's server time, outside which the EA ignores incoming signals[10]. Closing instructions are signals too, so plan the exits in the same way. On Edge the EA runs with fixed default settings that cannot yet be edited[8].
- Pausing automation for a weekend or an event: possible, but less clear. Stopping the alert in the alert manager is explicit and visible. A schedule can be forgotten and later copied into new alerts through sticky settings or a preset.
If a strategy should only trade in certain hours, put that rule where both entries and exits respect it, for example in the script's own logic, and keep the alert that carries its instructions on 24/7. Once a stop loss or take profit is set on an open position at the broker, it does not depend on a later alert. MetaTrader's help describes Stop Loss and Take Profit as executed on the trade server, working even when the platform is off, unlike its trailing stop[9]. Check the exact stop and target parameters in the PineConnector Syntax reference before relying on one.
Limitations and common mistakes
- Reading the Alerts log as proof of delivery. A logged trigger with a schedule attached may never have been sent. Use the Webhook status column as well[5], and look for the calendar icon.
- Sticky settings. A schedule chosen for one alert can become the default for the next one you create. Check the schedule on every new alert that sends to PineConnector.
- Presets. A preset can carry a schedule. Applying it to an automated alert brings the schedule with it. See what alert presets save.
- Changing your account time zone. The Help Center says the schedule follows the new time zone after the alert is restarted[2]. Until then, do not assume the window has moved.
- Muting to cover a machine that is switched off. A schedule does not keep MetaTrader running and does not replay signals later. If the reason for a schedule is that your computer is off at night, the terminal is the problem, not the alert.
What to check on an alert that feeds PineConnector
- Open the alert and confirm its notification schedule is 24/7, or that any other window is deliberate and also covers the exits.
- In the alert manager, look for the calendar icon next to each automated alert's status. Hover over it to see the days, hours and time zone.
- Confirm the Webhook URL box is ticked and the address is exactly
https://webhook.pineconnector.com[6]. - Check your presets and your last-used schedule, since both can carry a window into new alerts.
- Follow PineConnector's demo test workflow and compare the same trigger in three places: the TradingView Alerts log, PineConnector's Bridge, and the broker account[7]. A received signal, an accepted order, a filled deal and an open position are separate checkpoints.
If your self-hosted terminal is the reason you were tempted to mute alerts, PineConnector Edge is the relevant option: it hosts MT5 with the PineConnector EA, so the terminal does not depend on your own computer staying on. Edge currently runs the EA with fixed default settings and does not host third-party EAs[8]. It does not change what TradingView sends, so a muted trigger is still a muted trigger. The Edge page has the current plans.
Reviewed 23 September 2026. Facts were checked against the linked sources on that date. The examples are illustrative; no alert in this article was run against a trading account.
Related reading
- TradingView updates for alert-based automation: a practical index
- TradingView webhook received, but no MT5 trade: a stage-by-stage diagnosis
- How to set up TradingView webhook alerts
- TradingView alert presets: what they save and what you still enter
- What is PineConnector Edge? Hosted MT5, explained
Sources
- TradingView Blog – Notification scheduling for alerts has arrived, published 7 July 2026, updated 7 August 2026, accessed 23 September 2026.
- TradingView Help Center – Notification schedule for alerts, accessed 23 September 2026.
- TradingView Help Center – What timezone is displayed in alerts?, accessed 23 September 2026.
- TradingView Help Center – How to use a variable value in alert, accessed 23 September 2026.
- TradingView Help Center – How to configure webhook alerts, accessed 23 September 2026.
- PineConnector Docs – Troubleshoot an alert, accessed 23 September 2026.
- PineConnector Docs – Test your setup, accessed 23 September 2026.
- PineConnector Docs – Connect your MT5 account (Edge), accessed 23 September 2026.
- MetaTrader 5 Help – Trading operations: basic principles, accessed 23 September 2026.
- PineConnector Docs – EA settings reference, 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.
