-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Description
Describe the bug
I configured the watch as follows:
Today, I noticed that the watch was not working at all. Here is the log output:
2025-10-30 20:32:00.259 | INFO | changedetectionio.async_update_worker:async_update_worker:81 - Worker 9 processing watch UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 Priority 1761852720 URL <URL>
2025-10-30 21:31:46.596 | INFO | changedetectionio.async_update_worker:async_update_worker:81 - Worker 2 processing watch UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 Priority 1761856306 URL <URL>
2025-10-30 22:31:48.949 | INFO | changedetectionio.async_update_worker:async_update_worker:81 - Worker 8 processing watch UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 Priority 1761859908 URL <URL>
2025-10-30 23:31:19.275 | INFO | changedetectionio.async_update_worker:async_update_worker:81 - Worker 9 processing watch UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 Priority 1761863479 URL <URL>
2025-11-01 14:35:57.490 | INFO | changedetectionio.store:reload_state:99 - Watching: 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 <URL>
2025-11-03 16:18:49.622 | INFO | changedetectionio.async_update_worker:async_update_worker:81 - Worker 8 processing watch UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 Priority 1 URL <URL>
2025-11-03 16:18:49.623 | INFO | changedetectionio.realtime.events:handle_watch_operation:43 - Socket.IO: Queued recheck for watch 696fa094-35e1-478f-82ed-bd2e6c2fa4b0
2025-11-03 16:18:51.326 | INFO | changedetectionio.async_update_worker:async_update_worker:343 - Change detected in UUID 696fa094-35e1-478f-82ed-bd2e6c2fa4b0 - <URL>
Before the update on 2025-11-01 14:35:57.490, the check ran every hour as scheduled. Since the update, it hasn’t run automatically (I manually triggered it via the WebUI on 2025-11-03 16:18:49.622).
There are no errors in the log and no mentions of this watch except what’s in the code block above. All of the other watches that don't use the scheduler are working fine.
Version
v0.50.38
How did you install?
Container
Reactions are currently unavailable