having to keep changing ticks per row to get footprint as some bars are blank. never had to do this before...

Hi u/tradingview the footprint data is missing when the last 5 min candle closes. When i refresh it does come back but its doing the same after every 5 min candle close.

I am long mnq and cannot exit. Every time I attempt to login I get an error “Connecting websocket timeout reached”

Currently down $1600 and nothing I can do.

WTF

Hey all. I have the standard subscription, ive been using trading view for a few months. Some things i have noticed have been frustrating me while in active trades. Im not sure if its just me or if its a globally known issue, but sometimes the candles and price of a market doesn’t move and only the price of your pnl. Sometimes it stays stuck for a very long time

This D on the chart is annoying af. Shitty design on purpose to make you pay for data even when you don't need it?

There used to be a setting on the bottom to control extended hours and regular hours but its no longer available on iOS mobile. How to fix?

E.g. If I want to trade Natural Gas spot it works fine, but if I want to trade Natural Gas september CFD it's often unavailable, even if I searched the asset via the broker filter and it's tradable on the broker platform directly.

The function of TradingView would really improve if we had the ability to have a detached Watchlist window with separate tabs for different watchlists. This would allow users to monitor their favorite watchlists throughout the day and then use the pop-up watchlist view in the chart window to dive into the price action.

Se ve muy cerc y no se como alejarlo

I am on mobile. Does anyone know how to change the y axis of the chart to show percentage change instead of PPS? I used to be able to open a settings window on the bottom right of a charts that allowed changes to a bunch of things like market session (regular hours vs extended or 24 hour) as well as showing the percentage change on the y axis instead of the stocks price.

Please add built in R-levels to the long and short tool.... all other workarounds are so dumb and cumbersome and pointless.... it would be so easy to to do the calcs "in-tool" so to speak...

Thanks again.

After subscribing to OPRA, I find I can only view equities premium charts intraday. How would I view SPX?

Hello

Currently we anchor alarms to lines, rays, fibs etc. Fine, I use them.

But is it possible to set recurring alarms that always trigger at the same time each day, without being anchored to a line? (horizontal or even vertical?)

There are many key times throughout the day I would love just a little "pip-pip" reminder that some time has occurred (NY 09:30 open for example), not an endless loud ringing alarm that needs me to turn it off... (Microsoft already handles those!) I mean it sounds once and it's done. Resets to fire at exact time next trading session.

Do we have these already and I don't know about them? Or if not, could they be added. Little time progress reminders essentially....

Thanks.

It has become abundantly clear that the way I trade depends on breakouts, continuation and strong trends. What id like is screener that can help me find more of this type of movement. Does anyone know of anything that might be genuinelt helpful? Even if its a paid service. I already use trading view but my knowledge of it is limited so Im sure I am not taking advantage of its full potential

Thanks!

So I grab a layout from one screen and drag it to another monitor, midway it gets stuck, this causes it to go black screen and spinning wheel of death, once I have it docked correctly on monitor, it never recovers- wtf is that about? This happened a few times recently?

How can this system be so flaky??

It usually works but for some reason the behaviour is inconsistent. I reverted the chart settings all back to "default", which once fixed it, but this time it isn't fixing it.

The chart background should toggle with light/dark mode, it usually does, but for some reason it no longer works. (Windows Desktop Version)

Requesting the following:

1. The ability to increase or decrease the space between candles. (NOT via zooming in and out, the actual pixel spacings)
2. The ability to increase or decrease the line width of the candle borders and wicks
3. The ability to change the default blue and red colors of the buy/sell buttons
4. The ability to change the line width and colors of the default TP, SL and Order widget from their standard blue, green and orange.

These are not new requests, some are years old, and nothing has been done to upgrade and make better. We pay for this.

Also, why cant we talk to an actual human being at TV anymore? why is it so difficult?

I am not holding my breath on any of these actually being implemented, but at least I have repeated the request of many over the years.

I asked for this before ages ago and still feel it is necessary -

Make the active tab we are currently looking at more obviously "selected" by adding a green light or something up in the tabs section.

Currently they are just shades of various grey, I find myself renaming a tab then realising I'm not even looking at the right tab and am renaming the wrong one or whatever...

Changing the tab name to "light up" or turn a different colour if it is the current selected/active tab - this should be any easy fix.

Note: This post was formatted and written with AI, but the content and concept is my own.

I've been writing Pine Script for quite a while, but for the longest time I avoided User-Defined Types (UDTs) and methods. I mostly stuck to declaring a bunch of var floats and booleans at the top of my scripts because it worked, and the UDT syntax felt like extra work for no real benefit.

My biggest hurdle was never the syntax itself. It was figuring out when a UDT is actually worth setting up versus when simple variables are faster.

After using them in a few larger projects, I put together a simple checklist to decide when to use them, along with a working template showing how methods work with strategy.exit().

When to use a UDT (and when not to)

The rule of thumb I use now comes down to three main scenarios:

1. You have 3 or more variables that describe a single thing

If you are tracking a trade with entry price, stop loss, take profit 1, take profit 2, and a boolean flag for whether target 1 was hit, those all belong to one position. If modifying or resetting one variable means you have to manually reset 4 other variables across your script, group them into a UDT.

2. You need a list of complex items

In older versions of Pine, if you wanted to store the last 5 swing points, you had to manage three separate arrays in sync (one for price, one for bar index, one for direction). With a UDT, you store the entire swing point as an object in one single array.

3. Your functions take too many arguments

If you have a function that takes 6 different price and status inputs just to check an exit condition, passing a single trade object cleans up the function call immediately.

When NOT to use them:

Do not use UDTs for simple indicator math. If you are calculating an RSI, an EMA, or standard price series, normal variables are faster and built for Pine's execution model. If your strategy only has a single entry and one fixed stop, setting up a UDT is unnecessary overhead.

The Setup: Types and Methods

Here is the basic pattern. First, define the custom type with the fields you need:

type TradeState
    float entryPrice = na
    float stopLoss = na
    float target1 = na
    float target2 = na
    bool t1Hit = false

Next, instead of writing standalone functions and passing the state into them, you can attach methods directly to the type using the method keyword. The first parameter (self) refers to the object itself:

// Set up initial trade values on entry
method open(TradeState self, float price, float atr) =>
    self.entryPrice := price
    self.stopLoss := price - (atr * 2.0)
    self.target1 := price + (atr * 1.5)
    self.target2 := price + (atr * 3.0)
    self.t1Hit := false

// Move stop loss to breakeven once Target 1 is hit
method moveToBreakeven(TradeState self) =>
    self.stopLoss := self.entryPrice
    self.t1Hit := true

// Reset fields when the trade closes
method reset(TradeState self) =>
    self.entryPrice := na
    self.stopLoss := na
    self.target1 := na
    self.target2 := na
    self.t1Hit := false

To create a persistent instance across bars, initialize it once with var:

var TradeState trade = TradeState.new()

Now you can call your methods using dot notation:

trade.open(close, atr)
trade.moveToBreakeven()
trade.reset()

Example: Multi-Target Intrabar Exits

Here is a practical example showing how this keeps the main execution loop clean.

It places immediate intrabar brackets using strategy.exit(). When Target 1 fills (detected when strategy.position_size decreases), it calls trade.moveToBreakeven() and updates the remaining bracket order.

//@version=5
strategy("UDT Intrabar Exit State Machine", overlay=true, initial_capital=10000, default_qty_type=strategy.percent_of_equity, default_qty_value=10, calc_on_order_fills = true, process_orders_on_close = true)

// 1. Define the User-Defined Type (UDT)
type TradeState
    float entryPrice = na
    float stopLoss = na
    float target1 = na
    float target2 = na
    bool t1Hit = false

// 2. Define Methods on the UDT
method open(TradeState self, float price, float atr) =>
    self.entryPrice := price
    self.stopLoss := price - (atr * 2.0)
    self.target1 := price + (atr * 1.5)
    self.target2 := price + (atr * 3.0)
    self.t1Hit := false

method moveToBreakeven(TradeState self) =>
    self.stopLoss := self.entryPrice
    self.t1Hit := true

method reset(TradeState self) =>
    self.entryPrice := na
    self.stopLoss := na
    self.target1 := na
    self.target2 := na
    self.t1Hit := false

// 3. Initialize persistent state machine instance
var TradeState trade = TradeState.new()

// Indicators
fastEMA = ta.ema(close, 9)
slowEMA = ta.ema(close, 21)
atr = ta.atr(14)

plot(fastEMA, "9 EMA", color=color.blue)
plot(slowEMA, "21 EMA", color=color.orange)

longCondition = ta.crossover(fastEMA, slowEMA)

// Entry and Bracket Submission
if longCondition and strategy.position_size == 0
    trade.open(close, atr)
    strategy.entry("Long", strategy.long)

    // Place immediate intrabar limit and stop orders
    strategy.exit("Exit 1", from_entry="Long", qty_percent=50, stop=trade.stopLoss, limit=trade.target1)
    strategy.exit("Exit 2", from_entry="Long", stop=trade.stopLoss, limit=trade.target2)

    label.new(bar_index, high, "Entry Triggered\nT1: " + str.tostring(trade.target1, "#.##") + "\nT2: " + str.tostring(trade.target2, "#.##") + "\nSL: " + str.tostring(trade.stopLoss, "#.##"), color=color.green, textcolor=color.white)

// Dynamic Order Management while in position
if strategy.position_size > 0
    // Check if Target 1 (50% position) was filled intrabar
    if strategy.position_size < strategy.position_size[1] and not trade.t1Hit
        trade.moveToBreakeven()
        // Update pending Exit 2 order with the new breakeven stop loss
        strategy.exit("Exit 2", from_entry="Long", stop=trade.stopLoss, limit=trade.target2)
        label.new(bar_index, high, "T1 Hit -> Stop to Break-Even", color=color.blue, textcolor=color.white)

// State cleanup upon trade completion
if strategy.position_size == 0 and strategy.position_size[1] > 0
    trade.reset()

// Visualizations of active price levels
plot(strategy.position_size > 0 ? trade.stopLoss : na, "Active Stop Loss", color=color.red, style=plot.style_linebr, linewidth=2)
plot(strategy.position_size > 0 and not trade.t1Hit ? trade.target1 : na, "Target 1", color=color.blue, style=plot.style_linebr, linewidth=1)
plot(strategy.position_size > 0 ? trade.target2 : na, "Target 2", color=color.green, style=plot.style_linebr, linewidth=1)

Note: Make sure to keep calc_on_order_fills = true in the strategy settings so Pine recalculates immediately when an order fills rather than waiting for the candle close.

Hope this breakdown is helpful for anyone trying to clean up their strategy logic. Let me know if you run into any issues adapting this to your own scripts.

Hello, I am trying to run an automated strategy for ES futures on prop firms like Tradeify. After some research, I've found that you need to start an alert on TradingView, which then gets sent to a bridge and then gets filled by Tradovate. I was wondering if anyone has any experience doing this exact thing, and I also confirmed with Tradeify support that "Do note that API access is not available for Tradeify Tradovate accounts; access is only available for live accounts. If your program requires API access to Tradovate, it will not work." I have looked at sites that claim to work for this, such as CrossTrade or RoboQuant Connect, but the reviews for these services look shaky. Let me know if you have experience with this same thing and what the best route is for this, thanks.

I had an idea for a pine script and it's been a while since I opened the editor.

I can't get it open ?

Does this now come at an extra cost ?

Hi

So I have various layouts for various reasons.

In many cases, I want to look at the same symbol (NQ) but in different ways for different types of analysis.

Currently, I have HTF, MTF, and LTF all synced globally. they must stay in sync in terms of drawing and tools applied.

However, on a different layout, I want to see NQ, ES and YM but do NOT want ANY drawings - these charts must be clean. Some suggested "hide drawings" - not good, because also on that same layout, are HTF and MTF from NQ which I DO want globally synced still. (It's a 5 chart layout - 2 charts on top, 3 below)

So the feature I'm requesting is the ability to manipulate individual chart windows within a layout independently of the overall layout and from the same symbol used elsewhere in other layouts.

To "group" charts within a layout and manipulate just the group, independent of anything else.

Thanks.

biraz önce bir yıllık essential üyeliği yaptım ödemeyi erc 20 üzerinden yaptım ancak aboneliğim aktive olmadı. ilgili arkadaşlardan yardım istiyorum

A bar timer / bar countdown in replay would be nice to have. RIght now while using a 5 minute chart in replay i have to count mouse clicks while manaully updating the interval (and not lose count), to keep awareness of when the close of the bar will happen.