-
Notifications
You must be signed in to change notification settings - Fork 99
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
Tried to stop a LoopingCall that was not running #305
Comments
Any update on this issue? I also faced the same issue today. |
I got this error when my spider had a few timeout requests and spider close action was triggered but failed with following reason and later above error
|
Hello, could you please provide more details about this so we can replicate it? What Spidermon and Scrapy version were you using? What Reactor was installed? I see some weird URLS like: Are you sure the monitor and/or actions were properly configured? |
Hi @VMRuiz I actually added one "close spider" action dynamically if certain condition is fulfilled to the moniter suite that runs periodically We are using scrapy == 2.5.1 and spidermon == 1.17.0 versions. and twisted reacter is installed:
|
I also added two custom periodic monitors and imported monitor
I didn't find the reason that got this error.
The text was updated successfully, but these errors were encountered: