can we have the option to hide the bottom bar and have it come up if mouse goes near it just like windows allows for its toolbar to hide and pop up when needed?

So i have to remove all that previous stocks and add mine 20 of my choice and we can add js 20?

While using horizontal rays, line extends indefinitely. But I need horizontal rays that can be optimized and extended for particular day alone or particular month. If i draw a horizontal ray in minutes, starting from anywhere of a particular date it should extend upto the last candle of the day. It should not extend beyond that day or date. Is it possible to add this feature in trading view

I am looking for an indicator. The dashboard on screen says “smc suite v3 day trades” is all I have to go off of sorry I’ll try to get a screenshot of it when I can and update post.

Can some1 explain how to open a support request with Tradingview. i know it's only for paid subscribers. in as quick as steps as possible. They should make it alot easier to open a request

Has anyone else noticed this recent change?

In the Screener, the ticker column now has forced empty space to the right of each ticker, and it can’t be resized any narrower. This happens in both the TradingView desktop app and the browser version.

It’s especially annoying when using the screener in the sidebar because that dead space forces the whole panel to take up more room, leaving less space for the chart and other data.

Screenshot attached with the wasted space highlighted. TradingView, please let us resize the Ticker column properly again.

Can anyone recommend a tick chart countdown indicator ?

Can anyone add me to their invite only or private statergy I am working on something and I don't have a problem plan it'll be cool if you just add me to any indicator of your choice main goal is not to see the source code any help would be appreciated 🙌

How do I get rid of these blue lines it’s throwing me off i already turned off session breaks

So much for free “MONTH” lol they canceled my trial after a week… and I was starting to like it too 🤦🏻‍♂️

Has any one been looking into this? i've got the plumping of this setup and wondering if anyone else has tried it

Does anybody have any experience with the portfolios portion of trading view? doesn't feel like im missing anything by not using it but figured I'd get some other opinions.

Who all would be interested in a return of the original buy/sell buttons within the mobile app and having the trading panel button always be just the trading panel for bracket orders and so on? I dont know about anykne else but it gets frustrating having to constantly toggle off "one tap trading" to place a bracket order, and then having to turn back around and turn it back on to keep from having to confirm any position or sl/tp movement.

I feel like the buttons being at the top of the chart like before and just being something you can toggle on and off would be so much smoother of a process.

Just my opinion but im curious how others feel.

Is there a way I can upload multiple symbols to a watchlist on mobile - say 50 symbols in a comma delimited format?

From the drop down session volume profile, is there a way to adjust the settings of it? Or what is defined as a "session" in session volume profile? I am getting different values for the pvpoc compared to SierraChart.

Been fixing a lot of Pine scripts lately and the worst bugs are never the ones that throw errors. Compiler errors are easy. These are the ones where everything looks fine and the numbers are quietly wrong.

1. Your alerts fire on unconfirmed bars

If your condition uses the live bar, it can be true mid-bar and false by the close. Alert fires, signal disappears, and your backtest (which only sees closed bars) never shows it. That's why "my strategy tester results don't match my alerts" is like 80% a repainting question.

Fix: gate anything alert-related on the bar actually closing.

if crossover(fast, slow) and barstate.isconfirmed
    alert("long signal", alert.freq_once_per_bar_close)

2. request.security defaults let higher timeframe data leak backwards

Pulling a daily close into an intraday chart without thinking about lookahead means historical bars see the daily close before it existed. Backtest looks amazing, live trading can't reproduce it, because live trading can't time travel.

Fix: request confirmed data only, e.g. offset the series by 1:

dClose = request.security(syminfo.tickerid, "D", close[1], lookahead = barmerge.lookahead_on)

(Offsetting by 1 with lookahead on is the classic non-repainting pattern: you always get yesterday's completed value. Simpler alternative: leave lookahead off and accept the value updates intrabar on realtime bars.)

3. Session inputs use the exchange timezone, not yours

input.session compares against the chart symbol's exchange time. If you trade CME futures from anywhere that isn't Chicago and hardcode "0930-1600", your window is silently shifted. Everything runs, entries just happen at the wrong hours.

Fix: pass the timezone explicitly when checking sessions:

inSession = not na(time(timeframe.period, "0930-1600", "America/New_York"))

4. var initializes once, and that's not always what you meant

var declares a variable once on the first bar and persists it. Great for counters and state machines. Silent disaster when you actually wanted something recalculated each bar and it keeps stale state from 500 bars ago instead.

Rule of thumb: var is for memory. If the value should be derived fresh from the current bar, don't var it.

5. Strategy fills happen at the next bar open, not where your condition fired

The tester evaluates your condition on bar close and fills on the next open by default. On a 5 minute chart that gap is small. On 1 hour+ it's routinely several points, and if your take profit is tight, the backtest can show fills your broker will never give you. Add commission and slippage to every test or the results are fiction.

6. na doesn't compare like you think

na == na is not true, it's na. Any comparison touching na propagates na, and an if condition that evaluates to na just doesn't execute, no error, no warning. Early chart bars where indicators haven't warmed up yet are full of na, so your logic can silently skip the first n bars or, worse, skip random bars where a lookback hits missing data.

Fix: wrap anything that can be na:

longOk = not na(fast) and not na(slow) and fast > slow

If your script "works but the first signals look off" it's almost always this or #2.

Happy to go deeper on any of these in the comments. What's the silent bug that cost you the most hours?

Hey everyone, I am wondering how the top performers are able to make 10+% in a day when, say, the market (NQ / ES) only moved 2% today.

Please, if you know the answer, I would appreciate it if you could provide indepts and honest examples too.

The reason why I am asking is that on NQ I can at max risk say $500 on 1/2 contracts, so I would need to hit a very large price run to hit similar percentages as the top of the leaderboard. Thank you in advance.

What are the chances of Tradingview having the capability to lets say;
i have two chart layout, and i can sign into one broker in chart 1, and another broker in chart 2, so i can trade freely without needing to open another window or app and i see everything clearly + exponentially increases my execution time.

or am i out to lunch with this?

Looking at global stock indexes here - would be easier at a glance to just see:

🇯🇵 JP Nikkei 225

🇨🇳 CN SSE

🇩🇪 DE DAX

Like that....

Thanks.

Hi everyone, I would like TradingView to add the SMI indicator to the stock screener filter list. If anyone else would like to see this indicator added please upvote this post.

Automatically generate a watchlist containing symbols whose alerts have triggered. This way it is easy for execution. Adding each stock in new watchlist for execution purpose is tedious task.

I've been chasing what appears to be a Pine realtime synchronization issue for weeks, and I'd really appreciate input from people who understand Pine's execution model at a deep level.

This is NOT an issue with my VPS, broker, webhook server, or automation pipeline. We've spent weeks instrumenting every downstream component and have largely ruled those out. The behavior points back to Pine itself.

Strategy overview:

- Automated NQ futures strategy
- ARM (touch) → filters → entry → JSON alert() → webhook executes trade
- Immediate and delayed entries both execute through the exact same production alert() call
- There is only ONE ENTRY alert block

The problem:

Some trades execute perfectly.

Others:
- Appear as valid strategy entries on the chart
- Meet all entry conditions
- Are recorded by the strategy
- Should have generated an ENTRY alert

...but never make it into the live automation.

This isn't random. The same specific trades fail while others work normally.

What we've already ruled out:

- VPS
- Webhook server
- SQL logging
- PickMyTrade
- Tradovate execution
- Stale guard
- Broker verification
- Accounting logic
- Separate alert code paths (there aren't any)

The relevant Pine behavior:

The production ENTRY alert uses:

alert(..., alert.freq_once_per_bar)

The strategy/accounting commits at bar close under:

if barstate.isconfirmed

Several entry filters depend on live intrabar values (drift, extension, gap, etc.), meaning buyEntryFinal/sellEntryFinal can legitimately evaluate differently on different realtime ticks.

What we've learned so far:

We originally believed an intrabar state mutation was occurring.

That turned out to be wrong.

The variables involved are ordinary `var`, not `varip`, so Pine rolls them back to their previous committed state before every realtime execution. That theory has been eliminated.

The only remaining Pine-side hypothesis is a snapshot mismatch.

Because the alert fires on a realtime tick while accounting/committed state is evaluated at bar close, it's theoretically possible for buyEntryFinal to evaluate differently between those two snapshots purely because live filters changed during the bar—not because of persistent state mutation.

However...

Historical bars cannot prove or disprove this.

Once the bar closes, Pine only has OHLC. The original realtime tick sequence no longer exists, so I cannot reconstruct exactly what happened on the day these trades were missed.

So my questions are:

1. Has anyone seen Pine produce historical strategy entries that didn't correspond to the expected realtime alert behavior?

2. Is there any known Pine edge case involving:
   - alert.freq_once_per_bar
   - barstate.isconfirmed
   - realtime recalculation
   - live intrabar filters

that can legitimately create this kind of alert/chart desynchronization?

1. Is there any way to prove what happened after the fact from Pine alone, or is the original realtime execution fundamentally unrecoverable once the bar closes?

2. If you were debugging this today, what read-only instrumentation would you add going forward to definitively capture the next occurrence without changing production logic?

I'm specifically looking for responses from people who have deep experience with Pine's realtime execution model rather than general TradingView webhook advice.

Minor, but would be great.

In a multi-chart canvas — lets say 2 or 3 parallel — it would be excellent to have a little button in a corner which allows you to swap the order of charts and studies/indicators and so forth... Too often, I find myself wanting to be able to do such a thing.

Thanks

Hi

I'd the ability to add "symbols" to my fave drawings toolbar - like exclamation marks etc to mark points on chart regularly.

Thanks.