{{ message }}
Repository navigation
Conversation
github-actions
Bot
added
the
t-tooling
Mantisus
changed the title
run() callsrun() calls
vdusek
reviewed
Oct 21, 2026
Mantisus
force-pushed
the
update-purge
branch
from
October 21, 2026 17:23
f74cd16 to
1c2204f
Compare
vdusek
approved these changes
Oct 21, 2026
vdusek
changed the title
run() callsrun() calls
vdusek
approved these changes
Oct 21, 2026
vdusek
left a comment
vdusek
left a comment
Collaborator
There was a problem hiding this comment.
LGTM (I just changed the PR title to correspond with the JS one)
Co-authored-by: Vlada Dusek <v.dusek96@gmail.com>
Mantisus
force-pushed
the
update-purge
branch
from
October 21, 2026 17:38
1c2204f to
dddbade
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A repeated
crawler.run()no longer purges the request queue. It continues with the same request manager, so requests that an earlier run handled, failed ones included, aren't crawled again. Thepurge_request_queueargument ofrun()is removed, together with the named-queue and failed-run exemptions. JS v4 made the same change (apify/crawlee#4056). To crawl the same requests again, purge the request manager or open a fresh queue.A run that processes nothing while its request manager holds only handled requests now logs a warning explaining how to crawl them again. Unlike JS, the warning also requires the manager to be finished, so a crawl that
abort_on_errorstopped with requests still pending doesn't get it.RequestManagerTandem.purge()now purges the manager it wraps instead of doing nothing.RequestQueue.purge()no longer drops an unnamed queue and opens the default one in its place when the storage client can't purge. The client'sNotImplementedErrornow propagates, so on the Apify platform usedrop()or a fresh queue. The upgrade guide has a section for each change.Issues
run()calls #2305