[Bug]: Crawl4Ai pod goes unresponsive after few days of successful crawl #1754
Description
crawl4ai version
v0.8.0
Expected Behavior
Craw4Ai should not deteriorate after some days of crawling.
Current Behavior
After a few days of successfull crawling, I am getting this log in the crawl4ai pod
2026-02-10 06:59:17,220 - server - WARNING - Timeline update timeout after 4s
2026-02-10 06:59:26,221 - server - WARNING - Timeline update timeout after 4s
2026-02-10 06:59:35,223 - server - WARNING - Timeline update timeout after 4s
2026-02-10 06:59:44,225 - server - WARNING - Timeline update timeout after 4s
2026-02-10 06:59:53,226 - server - WARNING - Timeline update timeout after 4s
2026-02-10 07:00:02,229 - server - WARNING - Timeline update timeout after 4s
2026-02-10 07:00:11,231 - server - WARNING - Timeline update timeout after 4s
and this is forever. Crawl4ai pod becomes unresponsive. Can't start a new crawl, the ongoing crawl can't move further.
Only solution at this point is either restart the pod, or flush-all the Crawl4ai Redis. But thats not a proper solution.
Is this reproducible?
No
Inputs Causing the Bug
Steps to Reproduce
Code snippets
OS
Linux
Python version
3.12
Browser
No response
Browser version
No response
Error logs & Screenshots (if applicable)
No response