Reactor times out and doesn't give back any results

Hi. thank you the report. Could you share the log from console. Thanks

It doesn't give any logs back but gives an error 400, an unhandled error happened at the container or something.

This is my input: https://api.apify.com/v2/key-value-stores/9wgmsSLBUiv32i1xV/records/INPUT This is my output, I aborted after it took too long to give back results: https://api.apify.com/v2/logs/R8Ye1nYwMY97Btw2x I tried all of the types possible of proxies and still, can't search. I am attempting to search for a single vrbo property, it was working recently but since yesterday it no longer does.

And another log of yesterday of a failed instance:

2023-05-10T14:50:44.926Z ACTOR: Pulling Docker image from repository. 2023-05-10T14:50:45.675Z ACTOR: Creating Docker container. 2023-05-10T14:50:45.849Z ACTOR: Starting Docker container. 2023-05-10T14:50:50.168Z ☢️ Proxy enabled: http://:@dc.smartproxy.com:10000 2023-05-10T14:50:50.169Z ☢️ HTTP2 disabled. 2023-05-10T14:50:50.178Z 📝 Arguments: 2023-05-10T14:50:50.179Z ✅ location : Orlando, Florida, United States 2023-05-10T14:50:50.180Z ✅ adults : 18 2023-05-10T14:50:50.180Z ✅ min_bathroom : 5 2023-05-10T14:50:50.181Z ✅ min_bedroom : 9 2023-05-10T14:50:50.181Z ✅ limit : 500 2023-05-10T14:50:50.182Z ✅ includes : ['spaces', 'media', 'contact', 'amenities', 'description'] 2023-05-10T14:50:50.182Z ✅ filters : ['74'] 2023-05-10T14:50:50.183Z 📅 dates: DATELESS 2023-05-10T14:50:50.183Z 🐭 deploying 3 workers ... 🐸🐸🐸 2023-05-10T14:50:51.292Z ❌ Access errors #1. retry in 30 seconds ... 2023-05-10T14:50:55.181Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:00.182Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:05.185Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:10.186Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:15.187Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:20.188Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:22.415Z ❌ Access errors #2. retry in 30 seconds ... 2023-05-10T14:51:25.189Z 🐸 ... progress: 0/1 (0.0%) 2023-05-10T14:51:30.190Z 🐸 ... progress: 0/1 (0.0%) 2023-05... [trimmed]

Could you tried again. Let me know if its still a problem. I'll fix it ASAP

Hello, it's still not working. I've tried and it'd run infinitely for 10 minutes or so, I've noticed that VRBO have updated their website, can you recheck if the endpoints or selectors you're using to scrape the data are the same and unchanged? Please, we need this working again urgently. It'd be greatly appreciated if you could fix it ASAP. Thanks in advance and have a wonderful day.

Also, try to re-run the actor using this input I gave above and see if it works for you. Because I've tried a lot and it's not working at all.

Okay now after some retries, it worked twice but then started giving errors once again:

2023-05-11T19:45:27.163Z ACTOR: Pulling Docker image from repository. 2023-05-11T19:45:28.295Z ACTOR: Creating Docker container. 2023-05-11T19:45:28.798Z ACTOR: Starting Docker container. 2023-05-11T19:45:34.847Z 💤 waiting for other runs to complete ... [1] 2023-05-11T19:45:50.449Z 📝 Arguments : 2023-05-11T19:45:50.451Z ✅ location : 1124231 2023-05-11T19:45:50.452Z ✅ adults : 1 2023-05-11T19:45:50.453Z ✅ limit : 500 2023-05-11T19:45:50.454Z ✅ includes : ['contact', 'description', 'spaces', 'media', 'amenities'] 2023-05-11T19:45:50.454Z 🔎 pulling custom listing details ... 2023-05-11T19:45:51.460Z ❌ HTTP error 429: Too Many Requests 2023-05-11T19:46:21.995Z 💔 Failed Exception ... sad.

2023-05-11T19:47:33.526Z ACTOR: Pulling Docker image from repository. 2023-05-11T19:47:33.641Z ACTOR: Creating Docker container. 2023-05-11T19:47:33.771Z ACTOR: Starting Docker container. 2023-05-11T19:47:36.208Z 📝 Arguments : 2023-05-11T19:47:36.209Z ✅ location : 1124231 2023-05-11T19:47:36.210Z ✅ adults : 1 2023-05-11T19:47:36.211Z ✅ limit : 500 2023-05-11T19:47:36.212Z ✅ includes : ['contact', 'media', 'description', 'amenities', 'spaces'] 2023-05-11T19:47:36.213Z 🔎 pulling custom listing details ... 2023-05-11T19:47:37.131Z ❌ HTTP error 403: Forbidden 2023-05-11T19:48:07.702Z 💔 Failed Exception ... sad.

Hi, Thanks for your patient. I try to improve the actor so it could handle Access denied errors gracefully. Please try using Apify residential proxy or disable proxy. For specific listing IDs, I suggest requesting all at once instead one-by-one, to reduce rick of access error (403, 429, etc.) You can input it using location parameter: "ID1, ID2, ID3" or input multiple rows instead. Please inform me of any more errors, I'll be glad to help.

Okay, I'll test it around and let you know the results. Thank you!

Alright, it's stable so far. Thank you!

Hello, do you see those 3 images? Well, as I see, your actor is having a retry mechanism. Can you add an option somewhere for me to turn off these retries? So if I set retries = false or something, your actor doesn't retry. If any errors occurs, it fails immediately. As I've handles for this in my code and it'd make my code run much faster. Appreciate it. Thanks in advance!

Hey Michael 👋, I've added option in Advanced Options -> Disable Retries or dev_no_retry = true

Amazing, Thank you!

Hello, Can you explain what does "💤 waiting for other runs to complete (RUNNING) ... [15]" mean? Please make it as clear as possible. To my understanding, the actor waits for other Apify runs to finish? If that's correct, can that be disabled? This wastes a huge amount of time!

@cat