Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continue Scraping after API Key Limit Reached #414

Open
cbanack opened this issue Jul 25, 2015 · 0 comments
Open

Continue Scraping after API Key Limit Reached #414

cbanack opened this issue Jul 25, 2015 · 0 comments

Comments

@cbanack
Copy link
Owner

cbanack commented Jul 25, 2015

From here:

"Is it possible to have the scraper not completely quit and exit when the limit is reached, but offer an option to wait a bit and then hit something to continue (make it the non-default button). Would be nice to be able to queue everything up and then just periodically hit continue instead of starting over.

The issue I run into is if I queue up say 200, and it does 45 and quits, but 5 of those didn't auto-scrape when I restart it is going to re-attempt those 5 using up some of my searches. I'd like to be able to continue the queued up job after waiting. As of now, I have to do no more then 40-50 at a time which is brutal"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant