Suddenly "No parsable JSON found in this document" but filter preview still working fine #3135
Unanswered
andreagdipaolo
asked this question in
Q&A
Replies: 1 comment 5 replies
-
I got 403 from central europe, it could be that the JSON filter is trying to process the 403 document and not the json on the 'watch overview' listing page, what is the status, is it red? and where exactly does it say "No parsable JSON found.." ? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I was following marketplace listings with a Json filter on its search results and it was working fine, until April 15 at 13.00 Rome time.
Then, I stopped receiving notifications and the following day when checking for the reason I discovered the error "No parsable JSON found in this document".
But I tried everything and I cannot understand why it does that.
URL is https://hades.subito.it/v1/search/items?q=gameboy&t=s&qso=true&shp=true&urg=false&sort=datedesc&lim=5&start=0

It retrieves the last 5 ads, in this case.
It replies with json content both on my client and on the server I run changedetection on, so I have not been banned by the API.
I checked on https://jsonlint.com/ and the result is ok.
But most of all, if I run the filter preview in changedetection watch settings, it applies it as it should and it doesn't complain.

I updated the software to the latest version and it still gives the error.
I'm running this watch in plaintext mode.
Filters are:
I hope someone can help me find out what's happening.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions