My actors suddenly throw errors according to broken head in request queue
Hello together! I have a strange problem, my different actors working fine for months but suddenly they throwing errors like this:
according to my research this is caused by an empty or broken request queue. Sometimes caused by very long url with parameters and a broken unique id for the queue. But I don't use any long url and I use the apify request qeue like in the docs. If I run the actor on my local maschine all works fine. I spent days now to debug and find a solution so any help is welcome!
3 Replies
If somebody reads this post later on, this was caused by bugs in crawlee und apify which fixed in the actual versions:
GitHub
Apify RQ client
list_head method returns truncated unique keys an...Description When calling ApifyRequestQueueSingleClient._list_head(), the response contains truncated values of unique_key and url for long URLs. Longer than 128 chars, see https://github.com/apify/...
GitHub
Pydantic validation error in request queue after request retries ·...
Hello Apify devs! This week, my scraper which has been using crawlee[parsel] == 0.5.1 and apify==2.2.0 stopped working (returning 0 results, logs indicate the requests somehow getting blocked but I...