You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timeouts in user defined handlers should be treated the same way as other exceptions raised from within the user handler.
This should cause retry.
Currently the request that times out will end up in strange state in RequestQueue and it will block crawler from closing for 300 secs until following triggers:
"The request queue seems to be stuck for 300.0s, resetting internal state."
(Regarding blocking sync code timeouts from user defined handlers: #908)
The text was updated successfully, but these errors were encountered:
Pijukatel
changed the title
Timeout in user defined handler should cause retry
Timeout in user defined handler should cause retry (async blocking code)
Jan 15, 2025
Pijukatel
changed the title
Timeout in user defined handler should cause retry (async blocking code)
Timeout in user defined handler should cause retry
Jan 15, 2025
Timeouts in user defined handlers should be treated the same way as other exceptions raised from within the user handler.
This should cause retry.
Currently the request that times out will end up in strange state in RequestQueue and it will block crawler from closing for 300 secs until following triggers:
"The request queue seems to be stuck for 300.0s, resetting internal state."
(Regarding blocking sync code timeouts from user defined handlers: #908)
The text was updated successfully, but these errors were encountered: