Ajit - thank you very much for following-up on this!
What’s odd is that I already had the “Wait for duration” set to 10 seconds. I’m going to swap the JSON you’ve provided for the existing one, though (after customizing it for MSFT365Status).
Is there a chance I could ask you to use X in your monitor(s) and give it a day or two to see the “false positives” I’m sure you’ll see?.
one thing to note is that i used the desktop app to monitor this. twitter doesn’t load properly in a background tab in a regular browser as it needs the page to be active. the desktop app is better at loading such pages.
I’ve tried running this on the desktop app, and in the web browser (Edge) and am still getting false positives. For example, this change I just got alerted-on (top) was actually posted 4 tweets ago on 15-Apr. As a FYI, because of the need to be alerts as soon as possible, I have interval set to check every 15 minutes.
interesting to know that it works well for one case but not for the other.
was the content in red deleted or didn’t load in time for this check? if it was the latter, you will see the content revert back to the older value. you can try the following solutions:
increase the delay to a higher value and see if it helps.
if increasing the delay doesn’t help and content flip-flops, use the condition text doesn't match any previous text to silence the alerts due to flip-flops.
@ajitk - reporting back! LOL The condition you suggested seems to have fixed the issue. Thank you!
BTW, I noticed something odd about Microsoft’s posts, but it could just be that I’m unfamiliar with Twitter. Their original tweet stays at the top, but the newer ones are below it - are they replying to their own tweet? Is that why?