Zillow Detail Scraper
Pay $3.00 for 1,000 results
Zillow Detail Scraper
Pay $3.00 for 1,000 results
Get details of Zillow properties from URLs. This Actor can be easily integrated with other Zillow Scrapers.
Do you want to learn more about this Actor?
Get a demoGetting Warning errors
Closed
I see this in the log when the actor runs
2024-07-30T16:31:52.866Z ACTOR: Creating Docker container. 2024-07-30T16:31:53.006Z ACTOR: Starting Docker container. 2024-07-30T16:31:54.835Z INFO System info {"apifyVersion":"3.1.15","apifyClientVersion":"2.8.4","crawleeVersion":"3.7.2","osType":"Linux","nodeVersion":"v20.14.0"} 2024-07-30T16:32:02.050Z WARN Failed to populate cache for FOR_RENT, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:02.173Z INFO Verified query RECENTLY_SOLD with hash 3b123ac2c33226bce39c810f136361c1c7cb88993477a528019bb2a82d66bd1e 2024-07-30T16:32:02.556Z WARN Failed to populate cache for Building, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:02.930Z WARN Failed to populate cache for PaidBuilderHomeDetail, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:03.954Z WARN Failed to populate cache for FOR_RENT, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:04.691Z WARN Failed to populate cache for PaidBuilderHomeDetail, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:06.280Z WARN Failed to populate cache for FOR_RENT, retrying. Error: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON 2024-07-30T16:32:07.560Z INFO Verified query PaidBuilderHomeDe... [trimmed]
Hi, this is a known behavior. Sometimes, Zillow blocks our request and serves a HTML error page instead of JSON, which produces this error. We keep it in the log so that we can investigate when the scraper starts getting blocked more often or users report hard failures, instead of just warnings.
However, I understand that this can be confusing to end users. Thanks for raising this, we will reconsider it and eventually remove it from the log if we find that the information we get is not worth the confusion, or we can solve this in some other way.
I hope this helps, thanks for your understanding.
Best regards
Matěj
Maximillian Copelli- 134 monthly users
- 31 stars
- 98.8% runs succeeded
- 15 days response time
- Created in Jun 2023
- Modified 7 days ago
