I’m having trouble setting the conditions in distill for a website that gives a random result every so often. I will try to explain as simple as possible:
I’m monitoring the changing of a number on a website.
For example, the current text is 811. I get a notification when it changes to 812 (811 became 812). The next notification I receive is 815 (812 became 815). Then the monitored value changes to 175.548 (random event every so often). It is EU website, so 175,548 in US numbers. This event doesn’t trigger a notification because I have set Distill to only notify below 2000. Then the number changes from 175.548 to 821, which doesn’t trigger a notification. This is the part I’m having trouble with. I would like to somehow set the condition to receive a notification at this event but I’m having trouble finding the solution.
821 is lower than 175.548, but still higher than 815 (the number before the random event occurred).
I attached 2 screenshots. One is the list of events with the problematic event circled in red. The other one are the conditions I currently have set. Thank you for your time!
the second condition text has number that increased more than 0 will not be satisfied when the number changes from 175548 to 821. can you click the bell icon displaying notification status? it will show the how the conditions’ evaluation results were.
Hi Ajit, thanks for looking at this. The bell icon is displaying false on the second condition. I’m having trouble formulating a correct condition with this situation.
I gave these a try and it works (partially) Definitely on the right path with your help.
I am now getting a notification when for example 175548 changes to 821 which is great. However, i am running into a new issue with these conditions.
For example, 811 becomes 812 I receive a notification (all working as should). 812 becomes 815 I receive a notification (all working as should). Then the monitored value changes to 175548 (random event, no trigger), then back to 815. This is giving me a notification of 815 which I have already seen. This is creating a duplicate notification of 815 which happens after the random event.
I tried adding the ‘‘text doesn’t match any previous text’’, but I am introducing a risk of missing valuable content.
For example, 815 becomes 816 (I am notified), then 816 becomes 814 (not notified). Then 814 becomes 175548 (no notification, random event), then 175548 becomes 815 again (no notification, as the 815 is part of the previous text). Same would happen from 175548 to 816.
this is potentially missing the point of monitoring as the value represents new content posted.
if you need notifications for the same content that was seen in the past then text doesn't match any previous text will silence them. so it is not recommended in that case.
the best solution will be to not monitor the “random event” in the first place. does the page or that element contain some identifier (like a specific class or attribute) when the random event happens (besides the large number)?
