| ♥ 0 |
Hi, Is there a way to create an email/text alert when price hits a simple moving average line? I’ve been using a regular alert at the simple moving average price, but I’m having to update it daily. I was just wondering if there is an easier way to do this so that I didn’t have to update it daily, and the alert would follow the simple moving average line and automatically update. Thank you RESOLVED
Marked as spam
|
|
Private answer
Yep, you have a couple of options. You can create a Study Alert, set to auto recreate after being triggered. That works if you only have a handful of ticker symbols to apply this too. The other method is to create and save a custom scan, then build an alert from the saved scan. For your example there is no need to write any code, you can do this using the condition wizard. We have a few vides where you can learn these techniques and apply them to your specific case. The end of this video shows how to build alerts from a custom scan: https://www.hahn-tech.com/thinkorswim-overnight-range-scan-alert/ This video shows how to build Study Alerts: Marked as spam
 Posted by Pete Hahn (Questions: 37, Answers: 4087) Answered on September 6, 2017 4:33 pm
|
|
|
Private answer
Hi Pete, Thank you for your response. I tried to do the easier one (create a study alert) but it doesn’t seem to allow me to save it. Could you take a look to see if I’m doing it correctly? Thank you Attachments:
Marked as spam
 Posted by Sierra Golf (Questions: 3, Answers: 5) Answered on September 6, 2017 11:28 pm
|
|
|
Private answer
Thank you very much Pete! Marked as spam
Posted by Sierra Golf (Questions: 3, Answers: 5) Answered on September 8, 2017 10:36 am
|
First, notice there is an error message below the code block. “Wrong timestamp for on Dec-31-1969 18:00”.
I have never seen such an error message before but I can tell you there is no need to include:
(“period” = AggregationPeriod.DAY, “priceType” = PriceType.LAST)
You already have the study alert set to Day and the default price type for close is Last. It is redundant to include those. I can see that the condition wizard does allow you to build it this way, but that does not mean it is correct.
In case you are wondering what causes that error message. Remove the section that sets the priceType.