Login Page - Create Account

Home >> Support Board

Support Board

Date/Time: Wed, 08 Apr 2026 14:23:13 +0000

How to Post a Message for Support

Alert condition using Daily OHLC current day low (SG3[0]) does not trigger

View Count: 289

[2026-02-20 14:38:31]
[Go To First Post]
User138457 - Posts: 57
I am using an alert formula to detect when the low of the current candle is within a certain distance above a critical level. The logic works correctly with studies such as VWAP, VPOC, etc.,
but fails completely when using the Daily OHLC study current day low (SG3[0]).

My alert condition is:

AND(
abs(L[0]-ID15.SG3[0]) < ID60.SG4[-1]*ticksize,
L[0] >= ID15.SG3[0]
)

Where:

ID15 = Daily OHLC study
SG3 = Low
ID60.SG4[-1]*ticksize = proximity threshold

My intention is to detect when the current bar low is within a defined distance above the current day's developing low.

Observed behavior:
The condition works correctly if I replace ID15.SG3[0] with:
VWAP
VPOC
and other constant or intraday-updating reference levels

However, using ID15.SG3[0] (current day low), the alert triggers sometimes, sometimes not, even when the candle low is clearly within the threshold.

Visually, SG3[0] displays correctly on the chart and matches the current session low.
Date Time Of Last Edit: 2026-02-20 15:13:14
[2026-02-20 15:32:54]
[Go To First Post]
John - SC Support - Posts: 45542
We do not know what may be occurring. We do not see anything specific in the formula that would cause an issue.

You would have to check the values at each location where you think you should have the alert but are not getting it. You can get the values from the Tool Values Window. But we also recommend using the "Spreadsheet Formula" study, which, despite its name, uses the Alert Syntax. So you can enter pieces of your condition exactly as you have them and then build up, or use multiple copies in order to determine why you are not getting what you are expecting. Refer to the following:
Spreadsheet Formula
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-02-22 09:47:26]
[Go To First Post]
User138457 - Posts: 57
Sth is wrong here., see attached screenshot.
Even though the indicator paints correctly, it's values in the tool seem to be from the
preceding day, as clearly visible (value of line in the graph is smaller than the
"Daily low" in the tool window (highlighted). Any idea what is going on here? As you see in the tool config, the "reference days back" is set to 0,
as, I believe" it should. Very much puzzeled here.



https://www.sierrachart.com/image.php?Image=1771752854576.png
imageScreenshot 2026-02-22 102450.png / V - Attached On 2026-02-22 09:30:51 UTC - Size: 293.56 KB - 40 views
Attachment Deleted.
[2026-02-23 15:48:54]
[Go To First Post]
John - SC Support - Posts: 45542
We are not understanding the situation.

What are the values you are comparing? Where are they coming from?
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-02-25 08:11:20]
[Go To First Post]
User138457 - Posts: 57
I am comparing the "D-low" ("low" value from daily OHLC study) in the
"chart value for tools" with the value in the chart.
The tool claims that the daily low is at 6920.00 (marked line), WHILE in the chart it is at
6181.75. So in some way, event though the tool is set to use the same day (reference days back=0),
the tool (and hence prob. my query) sees "sth different"
[2026-02-25 14:47:54]
[Go To First Post]
John - SC Support - Posts: 45542
What is the Bar Period of the bars in that chart?

If they are 1 day bars, then you must have your crosshairs displayed on a different bar than the one you are referencing with the low of 6181.75.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-02-25 14:52:39]
[Go To First Post]
User138457 - Posts: 57
These are 5min bars. That is why I am so puzzled. This this all in the middle of 1 single day.
[2026-02-25 15:03:44]
[Go To First Post]
John - SC Support - Posts: 45542
Please get us that chart so we can take a look. Follow these instructions to get us the chart:
Support Board Posting Information: Providing Chartbook with Only a Single Chart

What is the date where that situation is occurring?
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-02-26 09:10:49]
[Go To First Post]
User138457 - Posts: 57
please find it attached
attachmentChartbook_ES_dlow_error.Cht - Attached On 2026-02-26 09:10:14 UTC - Size: 3.92 KB - 26 views
Attachment Deleted.
[2026-02-26 15:20:43]
[Go To First Post]
John - SC Support - Posts: 45542
We are not seeing any issues with the chart and with the Daily OHLC.

The one thing we want to point out is that you have the "Daily OHLC" set to "Graph High and Low Historically" to "Yes". As such, the value displayed in any particular bar will be the value of the low for that bar. From the original image you posted, the last bar to the right has a new low and the previous bars before it have values that are higher than it. We can not see what bar the crosshairs are set to in that particular image, but it must be a bar where the low happened to be at 6920.00.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-03-02 19:58:33]
[Go To First Post]
User138457 - Posts: 57
I redid my chartbook essentially from scratch, that solved the issue, sth weird happend, nevermind.
As it is connected to the same thing I want to solve, I'd like to ask here briefly, if I may:

What is currently the length maxima for alert conditions? I could only find old posts from 2019, where an extention
within 1-2 years was discussed, but nothing "current", I also was unable to find anything in the documentation
[2026-03-03 06:39:59]
[Go To First Post]
Sierra_Chart Engineering - Posts: 23454
There is not really a limit, but somewhere in all of the processing there might be some limit but it would be very high. We are not sure what it would be, but it would be very high and very unlikely to ever be encountered. It would take research to look into this.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2026-03-03 06:40:33
[2026-03-03 07:27:07]
[Go To First Post]
User138457 - Posts: 57
That is interesting, as in the following the last 2 lines appear to never execcute


OR(
AND(
abs(H[0]-ID5.SG1[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID5.SG1[0]
),
AND(
abs(H[0]-ID19.SG2[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID19.SG2[0]
),
AND(
abs(H[0]-ID19.SG3[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID19.SG3[0]
),
AND(
abs(H[0]-ID19.SG4[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID19.SG4[0]
),
AND(
abs(H[0]-ID25.SG2[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID25.SG2[0]
),
AND(
abs(H[0]-ID25.SG3[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID25.SG3[0]
),
AND(
abs(H[0]-ID25.SG4[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID25.SG4[0]
),
AND(
abs(H[0]-ID14.SG4[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID14.SG4[0]
),
AND(
abs(H[0]-ID12.SG2[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID12.SG2[0]
),
AND(
abs(H[0]-ID12.SG3[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID12.SG3[0]
),
AND(
abs(H[0]-ID20.SG1[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID20.SG1[0]
),
AND(
abs(H[0]-ID20.SG2[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID20.SG2[0]
),
AND(
abs(H[0]-ID20.SG3[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID20.SG3[0]
),
AND(
abs(H[0]-ID20.SG4[0])< (ID60.SG4[-1]*ticksize),
H[0]<=ID20.SG4[0]
),
AND(
abs(H[0]-ID6.SG2[0])<= (ID60.SG4[-1]*ticksize),
H[0]<=ID6.SG2[0]
),
AND(
abs(H[0]-ID6.SG3[0])<= (ID60.SG4[-1]*ticksize),
H[0]<=ID6.SG3[0]
)
)
howewver, when I restrict to these last two

OR(
AND(
abs(H[0]-ID6.SG2[0])<= (ID60.SG4[-1]*ticksize),
H[0]<=ID6.SG2[0]
),
AND(
abs(H[0]-ID6.SG3[0])<= (ID60.SG4[-1]*ticksize),
H[0]<=ID6.SG3[0]
)
)
it executes flawlessly, so I had assumes a "limit" being the problem
[2026-03-03 07:32:03]
[Go To First Post]
Sierra_Chart Engineering - Posts: 23454
We will check on this.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

For the most reliable, advanced, and zero cost futures order routing, use the Teton service:
Sierra Chart Teton Futures Order Routing
[2026-03-03 07:40:03]
[Go To First Post]
User138457 - Posts: 57
Very much appreciated
[2026-03-03 14:19:14]
[Go To First Post]
Sawtooth - Posts: 4324
There is a character limit to Alert formulas.
Is there a character limit in Simple Alerts formulas?
[2026-03-03 14:45:27]
[Go To First Post]
User138457 - Posts: 57
But these posts are from 2013 and 14, which is precisely why I was asking
[2026-03-04 14:31:44]
[Go To First Post]
Sawtooth - Posts: 4324
I removed all of the [0]s that are not required, reducing the character count by 192.
I also removed all of the spaces, and all but 17 line feeds.

Try this:

OR(
AND(abs(H-ID5.SG1)<(ID60.SG4[-1]*ticksize),H<=ID5.SG1),
AND(abs(H-ID19.SG2)<(ID60.SG4[-1]*ticksize),H<=ID19.SG2),
AND(abs(H-ID19.SG3)<(ID60.SG4[-1]*ticksize),H<=ID19.SG3),
AND(abs(H-ID19.SG4)<(ID60.SG4[-1]*ticksize),H<=ID19.SG4),
AND(abs(H-ID25.SG2)<(ID60.SG4[-1]*ticksize),H<=ID25.SG2),
AND(abs(H-ID25.SG3)<(ID60.SG4[-1]*ticksize),H<=ID25.SG3),
AND(abs(H-ID25.SG4)<(ID60.SG4[-1]*ticksize),H<=ID25.SG4),
AND(abs(H-ID14.SG4)<(ID60.SG4[-1]*ticksize),H<=ID14.SG4),
AND(abs(H-ID12.SG2)<(ID60.SG4[-1]*ticksize),H<=ID12.SG2),
AND(abs(H-ID12.SG3)<(ID60.SG4[-1]*ticksize),H<=ID12.SG3),
AND(abs(H-ID20.SG1)<(ID60.SG4[-1]*ticksize),H<=ID20.SG1),
AND(abs(H-ID20.SG2)<(ID60.SG4[-1]*ticksize),H<=ID20.SG2),
AND(abs(H-ID20.SG3)<(ID60.SG4[-1]*ticksize),H<=ID20.SG3),
AND(abs(H-ID20.SG4)<(ID60.SG4[-1]*ticksize),H<=ID20.SG4),
AND(abs(H-ID6.SG2)<=(ID60.SG4[-1]*ticksize),H<=ID6.SG2),
AND(abs(H-ID6.SG3)<=(ID60.SG4[-1]*ticksize),H<=ID6.SG3))
Date Time Of Last Edit: 2026-03-04 15:06:14
[2026-03-05 09:36:12]
[Go To First Post]
User138457 - Posts: 57
Thanks for the effort, but doesn't change the problem
"last 2 lines don't work if in the full statement, but work perfectly if restricted to the last 2"
at all.

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account