I’m getting notifications for alerts which should not be triggering due to the stated Added Text condition not being met.
For instance, with some of these alerts, the only field changing is a number—-say, 2 changing to 5—whereas the Added Text regex specifies specific words being changed or added. I even looked at the change history to verify no other elements would be highlighted ‘green’. The text in question is present on the page; it just isn’t among the text that was added or changed.
What’s strange is that I do not have the same problem if using this Added Text regex filter with the individual monitors themselves (ie, those alerts would no longer be triggered); it is only failing when used as a Global Condition for whatever reason.
@shadowmoses condition debugger is a great way to understand what could be going on. click the bell icon (displays trigger status) in the change history and let me know what you see. thanks!
Thanks for the response (back then!). I figured things out eventually. Just got myself confused it would seem.
However, now I have a separate issue with specific monitors for a particular site meeting the “True” conditions but not being recognized as such (in other words, the history entry doesn’t turn “white” to signify a new matching result). I even tested the monitors with “Test Conditions” and it shows the final result to be true (no Global Conditions applied fwiw). And I get the same result regardless of the device used. Can’t put my figure on what the issue could be. Any ideas?
EDIT- To be more specific, the monitors in question only include a basic “Text” condition. And from what I can tell, they are only triggering when there would be a change in text detected on the page even though they are set up to trigger every time the “Text” condition would be met irrespective of any changes being detected. Is this by design or unexpected behavior?
