Booking Scraper

Hi Jan, thanks a lot for reporting this! We've just updated this Actor with a fix that should hopefully resolve this ;) It seems like a one time error probably caused by Booking. Still we've found and fixed a small error, that could've been the cause of this.

Is there some issue with the proxy? Yes and no, the reported error is a form of Booking's silent blocking (blocking the proxies). Though the Actor is setup so that everyone is running the same proxies, so that shouldn't be it.

Try it out and let me know how it works now, thanks!

Hello,

thank you for investigating the issue. Unfortunately, the fix didn't help and crawler is still returning same results (no results with the same issue). I can share in DM with you another link to run with latest build (0.0.23), if it will help. Thank you!

Hi again, thanks for the update. Yes, you are right, it turns out we forgot to fix the problem for the initial starting pagination page. So only the second and further paginations are currently fixed. We plan to release an update tomorrow, which should greatly increase the speed of this scraper. We will add the (hopefully) final fix into the update with it ;)

Thank you for your understanding!

Hi there, sorry we took a day longer to release, but I'm happy to inform you now, that we just updated the Actor with the final fix ;) This update also includes a significant improvement in scraping speed.

Try it out and let me know how it works, thanks!

Ok this is really really weird. I just run the Actor through your account and got no results, yet running it on from my account with the same proxies as your account has, yields the expected output. I will discuss it with the team, thanks a lot for your patience!

Hi again, this time it's the actual final final fix ;) Tested it on your account and it works well. Also reverted back the used credit's and runs.

Thanks a lot for your patience and happy scraping!