The strange thing is it's seems I have all announce but state of scraping is "error" without any more information

maybe this is related to this task (https://console.apify.com/organization/TzEYl4RGm5rKPyOU5/actors/dqFjeUv7Nrv7lRatk/runs/W5LcRWfuJhS23dffM#log) because it's seems an actor change host during execution and delist all announce but I don't know how fix that

I'll check and get back to you 🙂

I don't have access to the this link https://console.apify.com/organization/TzEYl4RGm5rKPyOU5/actors/dqFjeUv7Nrv7lRatk/runs/W5LcRWfuJhS23dffM#log

2025-03-13T10:00:05.629Z ACTOR: Pulling Docker image of build xtcRdB7ftswfAg7DP from repository. 2025-03-13T10:00:06.240Z ACTOR: Creating Docker container. 2025-03-13T10:00:07.158Z ACTOR: Starting Docker container. 2025-03-13T10:00:10.016Z INFO System info {"apifyVersion":"3.3.2","apifyClientVersion":"2.12.0","crawleeVersion":"3.13.0","osType":"Linux","nodeVersion":"v20.18.3"} 2025-03-13T10:00:10.145Z bypassing bot protection... Please be patient :) 2025-03-13T10:05:57.021Z WARN Request: We've encountered a POST Request with a payload. This is fine. Just letting you know that if your requests point to the same URL and differ only in method and payload, you should see the "useExtendedUniqueKey" option of Request constructor. 2025-03-13T10:08:26.830Z pass through.... 2025-03-13T10:09:18.456Z ACTOR: Notifying Actor process about imminent migration to another host. 2025-03-13T10:09:34.168Z ACTOR: Run was migrated to a new host. 2025-03-13T10:09:34.172Z ACTOR: Pulling Docker image of build xtcRdB7ftswfAg7DP from repository. 2025-03-13T10:09:35.091Z ACTOR: Creating Docker container. 2025-03-13T10:09:56.993Z ACTOR: Starting Docker container. 2025-03-13T10:10:01.031Z INFO System info {"apifyVersion":"3.3.2","apifyClientVersion":"2.12.0","crawleeVersion":"3.13.0","osType":"Linux","nodeVersion":"v20.18.3"} 2025-03-13T10:10:01.140Z bypassing bot protection... Please be patient :) 2025-03-13T10:10:42.475Z WARN Request: We've encountered a POST Request with a payload. This is fine. Just letting you know that if your requests point to the same URL and differ only in method and payload, you should see the "useExtendedUniqueKey" option of Request constructor. 2025-03-13T10:16:08.554Z pass through.... 2025-03-13T10:16:10.461Z Monitoring mode enabled 2025-03-13T10:16:10.463Z New items: 0, Delisted items: 7508

Hmm, thanks.

This seems to have been caused by what they call actor migration: https://docs.apify.com/academy/expert-scraping-with-apify/migrations-maintaining-state. Since running actors are essentially Docker containers, they can change hosts at any time. If an actor takes a relatively long time to run, there's a high chance it will be migrated, causing its state to be erased.

Now, since this started full deep scraping again, not sure what was the error (I disabled logs but will enable them so we can check the failure you have). FYI, I tried this on my end and it was OK (Using a different search url)

Have you tried scraping a smaller result?

Have you tried triggering the same scraper but without deepScrape?

Have you considered scraping without the deepScrape option? (I'm just referring to whether the information you're looking for exist in the paginated scrape without scraping individual ads. I suppose there would be some changes to implement in your integration, but let's first confirm whether deep scraping is an absolute necessity)

(Please don't trigger the same deepScrape because it'd add unnecessary load to their website without yielding results, don't until we figure this out)

We need deepscrape (some details are not in paginated info) and for this exact search.

I can make some test to determine if some params impact run (by example container memory)

Should I switch version to enable debugging ?

I'll enable it only for your Apify username. Could you please mention it here? Also:

• Have you tried scraping a smaller result?
• Have you tried triggering the same scraper but without deepScrape?

Hi,

We run task in our organization TzEYl4RGm5rKPyOU5 (xo7) and my username is (jeremy.xo7)

Today I have a timeout without error after 1h38 (but without output)

• I run without deepScrape and without delta mode and it’s work
• I upgrade memory (and cpu) for tomorrow run (I will see if this change something)
• I test with smaller results it’s work too

For information I run task daily (with deepScrape & monitoring) and before 3 days everything work all month long

Thanks, just one more question: are you scraping the same URL every-time?

I also see (in your screenshot) that an actor migration happened again... I suspect that something happened at Apify's level recently where migrations became more frequent than before

Yes

I've just posted this in Apify's Discord group (feel free to hop in: https://discord.com/channels/801163717915574323/1351743496251379763/1351743496251379763).

In the meantime, I suggest you avoid triggering such large-scale scraping. I'll enable debugging for your username and add a task to revamp the actor so it can gracefully handle potential migrations.

Sorry for the inconvenience—ETA is around two weeks. I plan to work on this over the weekends of the 22nd-23rd and 29th-30th, but if I have more bandwidth, I'll try to get it done by the start of next week