You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which package is this bug report for? If unsure which one to select, leave blank
None
Issue description
The requestsRetries statistics are only updated once the request is fully handled (succeeds or fails). This creates a false notion that requests are not erroring as much. The problem is made worse by that after error, requests are pushed at the end of the queue which means for a long time, there will be requestsRetries: 0 while significant requestsFinished. At the end of the Crawler.run, the retries will show correct number if all the requests were finished but imagine if the crawler gets .teardown or crashes.
I don't see any use-case for having the retries added only once handled so I consider this a bug.
Which package is this bug report for? If unsure which one to select, leave blank
None
Issue description
The requestsRetries statistics are only updated once the request is fully handled (succeeds or fails). This creates a false notion that requests are not erroring as much. The problem is made worse by that after error, requests are pushed at the end of the queue which means for a long time, there will be
requestsRetries: 0
while significantrequestsFinished
. At the end of the Crawler.run, the retries will show correct number if all the requests were finished but imagine if the crawler gets.teardown
or crashes.I don't see any use-case for having the retries added only once handled so I consider this a bug.
See also run on Apify https://console.apify.com/view/runs/cbHWZTetxgehJuK3b
Code sample
Package version
3.11.5
Node.js version
20.12.2
Operating system
No response
Apify platform
I have tested this on the
next
releaseNo response
Other context
No response
The text was updated successfully, but these errors were encountered: