Support Board
Date/Time: Sun, 15 Jun 2025 16:05:05 +0000
TPO Study and Chart Drawing Alert
View Count: 217
| [2025-06-05 11:25:21] |
| User173763 - Posts: 10 |
|
Hello SierraChart Team, I have configured a chart drawing alert on a simple line that is initially orange. The alert works perfectly on charts that display Bars: when the price crosses the line, the line color changes to Green, and the alert triggers as expected. However, when I apply the exact same setup on a chart that includes the TPO study, the alert does not trigger. My assumption is that this happens because the alert condition relies on bar data for calculation, but the TPO chart displays blocks (letters) instead of standard bars. As a result, the alert condition may not be evaluated properly on the TPO chart. Could you please confirm if this is expected behavior and advise if there is a workaround to enable alerts based on drawing color changes or price crossing in conjunction with TPO charts? Thank you in advance ! |
| [2025-06-05 15:04:34] |
| John - SC Support - Posts: 40422 |
|
There are some items that will work for an alert on a drawing with a TPO chart (such as the Last being Above or Below), but the CROSSING option does not work. Depending on what you want to do, you might be able to create a Study Alert that will accomplish what you want. Refer to the following for how to reference drawings in alerts: Study/Chart Alerts And Scanning: Referencing Chart Drawings For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-06-07 04:13:47] |
| User173763 - Posts: 10 |
|
Thanks, that did help! You are right that the Last Being Above or Below condition is calculated correctly. From what I understand, the alert system evaluates conditions by comparing with the multiple timeseries on the chart, and when I open the Tools Value Window on a chart with a TPO study, I can see the Last timeseries present, similar to a regular bar chart. However, I’m curious why the CROSSING condition doesn’t get calculated or trigger on the TPO chart, even though Above and Below do. What is the logic under it ? Appreciated |
| [2025-06-09 15:17:11] |
| John - SC Support - Posts: 40422 |
|
Without digging into the code, we cannot answer this question, and quite honestly, we just do not have the time to dig into it to answer this question. Suffice it to say that it just does not work due to how the TPO chart is handled internally.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-06-09 19:23:38] |
| User173763 - Posts: 10 |
|
Hi Sierra Chart Team, Thank you for your answer. (Notice the greeting—common in human interaction and reflects a basic level of politeness.) I genuinely value your time and the effort it takes to respond to user questions. (Notice that I’m not being dismissive, nor do I assume my time is more valuable than others’. That said, your response gives the impression that less than 10 seconds were spent formulating it.) Now, to the core issue: To my knowledge, there is no mention in the documentation that the CROSSING alert condition is unsupported for chart drawings when used in conjunction with TPO charts. As a result, when this condition fails—while ABOVE and BELOW work as expected—it creates a lack of clarity in both the platform’s behavior and its documentation. Without knowing the root cause of this inconsistency, it becomes impossible to determine whether similar undocumented or buggy behavior may be present elsewhere in the system. (Notice the structured framing of the issue—coming from a long-standing IT professional background where clarity and transparency in system behavior are fundamental to diagnosing and resolving technical problems.) I do understand that it currently doesn’t work. (Notice I maintain a respectful tone, even though the phrasing “it just doesn’t work” sounds less like a professional technical response and more like something you’d hear from a teenager explaining why the Xbox won’t turn on after spilling Coke on it. If you are, in fact, a teenager helping out at the support desk this summer—my apologies. Please take this as a recommendation: in professional environments, we explain rather than evade. That’s how credibility and user confidence are built—especially when software behaves in undocumented or inconsistent ways.) I’m asking that you spend some time looking into this further—not out of entitlement, but because understanding the why is critical to ensuring reliable and predictable use of the platform. Inconsistencies like this deserve technical acknowledgment and, ideally, documentation—whether they’re design limitations or oversights—so users don’t waste time chasing behavior that can’t be reproduced or explained. Best regards, Leonidas |
To post a message in this thread, you need to log in with your Sierra Chart account: