{
"selections": [
{
"frames": [
{
"index": 0,
"excludes": [],
"includes": [
{
"expr": "main",
"type": "css",
"fields": [
{
"name": "text",
"type": "builtin"
}
]
}
]
}
],
"dynamic": false,
"delay": 0
}
],
"regexp": {
"expr": "",
"flags": "gim"
},
"ignoreEmptyText": true,
"includeStyle": false,
"viewport": {},
"dataAttr": "text"
}
@stdedos the log shows that monitor has been checked everyday. but the content doesn’t appear to have updated. i am curious why that could be. for example, could it be browser’s cache? as a test, can you duplicate the monitor check what is captured in the first change history? thanks!
I don’t understand what I should do 
oh, sorry. the second screenshot in your post is from the change history. i wonder what it will look like in the duplicated monitor.
Today it “updated” - but those posts are from 2d ago (monitor every 6h)
one of the potential reasons could be browser’s cache loading older page instead of the new one.
… how can that be, when just opening that URL in the browser “just works 
”?
“In any case”, Distill should somehow be able to force a refresh?
distill loads the page in a tab and leaves the rest to the browser. if the browser’s cache is an issues, try cleaning it using an extension. you can try using a cloud monitor as a backup.
I think we are talking past each other.
When I manually navigate to that page, page renders correctly.
Distill fails to “somehow see the new one”.
does the monitor not see the latest post even now?
i thought it was able to after the “update”.
if it is still not able to view the latest post, try creating a new monitor for the page and make sure to keep javascript enabled. once the check succeeds, let me know what the monitor sees in the change history.