Resume crawler based on request queues from previous run locally and in apify

The community member is asking if it is possible to stop a crawler and resume it from the previous run's request queues, in order to add proxies and speed up processing without starting from scratch. The comments suggest that using a named request queue instead of an unnamed one can help, as the named queue is persisted. Another community member also mentions that the process can be canceled and restarted without purging the storage, using the crawlee run --no-purge command. The community members also note that Apify is working on a graceful abort feature to address this issue.