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

Zero actions counter and Standard Update #88

Closed
bezkos opened this issue May 31, 2017 · 2 comments
Closed

Zero actions counter and Standard Update #88

bezkos opened this issue May 31, 2017 · 2 comments

Comments

@bezkos
Copy link

bezkos commented May 31, 2017

When u set a field as Standard Update and there are new updates on that specific field then zero actions counter keep increasing +1 instead of staying in previous value.
With current state, dynamic scheduling will go to max_time even if there are regular updates on Standard Update field.

@holgerd77
Copy link
Owner

holgerd77 commented Jun 1, 2017 via email

@holgerd77
Copy link
Owner

Hi, I've added this for the upcoming v.0.12.2 release (couple of days). A field update is now also treated as a successful action causing the zero actions counter to reset, so working with scheduling when using STANDARD (UPDATE) fields should now work more like one would expect.

holgerd77 pushed a commit that referenced this issue Jun 7, 2017
…sful action causing the scheduler to reset the zero actions counter and not increase time between scraper runs up to the max time (#88)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants