If a monitor is true in the initial test, but then is not true anymore, after taking the conditions into account, like “text does not include …”, then it appears in the unread section, only not bold.
The correct behavior would be to not appear there, at all.
if a change recorded for a monitor triggered a change, that monitor will remain unread even if subsequent changes didn’t match conditions. this is working as designed. this ensures that user doesn’t miss that an important change event.
It happens, for example, with this link: 5 Encord jobs in Worldwide
Additionally I check for the message, that no jobs were found. And I exclude this as a condition.
The page then regularly appears in the unread tab, but without an alert and without being written in bold.
{
"ignoreEmptyText": true,
"includeStyle": false,
"dataAttr": "text",
"selections": [
{
"frames": [
{
"index": 0,
"excludes": [
{
"type": "css",
"expr": "li .job-card-list__footer-wrapper"
},
{
"type": "css",
"expr": ".artdeco-toggle–default"
}
],
"includes": [
{
"type": "css",
"expr": ".scaffold-layout__list",
"fields": [
{
"name": "text",
"type": "builtin"
}
]
},
{
"type": "css",
"expr": "[aria-live=‘assertive’] .t-normal",
"fields": [
{
"name": "text",
"type": "builtin"
}
]
}
]
}
],
"dynamic": true,
"delay": 15
}
],
"incognito": false,
"regexp": {
"expr": "",
"flags": "gim"
},
"blockAdsAndCookies": true
}
I don’t think, it should work like that. Since if a monitor fails, because of a “text does not contain”, then it will not be in the unread tab, if one is not already in the unread tab. It only appears there, without being bolded, if one is waiting in the unread tab.
the config json looks standard but something looks off. if a monitor is unread, the monitor will appear in bold in the watchlist.
let me know what you observe.
I’m not sure, what you mean with unread count, I don’t see additional info, after sending it to trash.
The change log states even, that some minutes ago a change happened, but it was not bolded and no alarm sound happened. It just sits there. Partly this is correct, since the page content shows random jobs, that I also can not exclude, but the page shows a string, that claims that no jobs could have been found, as well. And I say, that this string should not lead to an alert. But it staying in the unread tab, must mean, that the string condition checks must have happened after some of these other checks already logged, that a change happened.
With another monitor I found a slightly different issue. I excluded “Loading…” because sometimes a part, that shows a number, does not fully load. Now I still get alerts, whenever a zero was found.
To be more exact, the monitor finds “Loading…”, and for this monitor, it does not appear in the unread area. But then I get an alert, when the next check happened because it found “0” instead of the “Loading…”.
Which in reality means, I get alerts for zeros again and again because it stored the “Loading…” as a page change. Normally I should not get the alerts, since the real website content was 0 before, as well. It alerts me about the zero, all the time.
To make the problem a bit more visual. I constantly get alarms for this. Sometimes part of data of the page is not fully loading, that does also not change with more time. It’s some kind of missing response, and no new request is sent.
But when this happens, then it seems to internally log this as content change. It does not alert me because I have a rule for “Text, does not contain “Loading…”” and so it does not alert.
However, when the page loads fully the next time, I will receive an alert, despite the website not having changed. There are still zero data rows available.
I would like to prevent these alerts, ideally not logging a website change if the condition should exclude it.
a macro’s panic function should help validate page’s content. if the page’s content is not valid, one can wait for a longer duration or even error out the check. for example, panic function can error out the check if a criteria is met.
here is a sample usage of the panic function:
panic(element_has_text(<element_selector>, "Loading"), )
if the macro panics and raises an error, this check will error out instead of capturing this as a change.
The website is always showing “Loading…” first. Wouldn’t it panic before?
Also, is there documentation about this command? I could only find it being mentioned on the forum.
use one of wait_for_duration or wait_for_element functions to make sure that you have waited enough.
the macro editor itself displays the documentation of the function. hover over the function after adding it. it will then display the documentation of the function. the signature is panic(condition: boolean, code: string[, message: string]). when a condition is true, the panic raises an error with the given error code and message. here is how to view and use it:
