scheduler not working

[allddd]

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

[dgtlmoon]

"Today, I noticed that the watch was not working at all. Here is the log output:"

I'm sorry but that is not enough information. There should be more output through the day for sure

Can you show the logs on the turn of the hour? Maybe adjust the watch so it will run on more hours so you don't have to wait until tomorrow?

And can you send me your url-watches.json?

[dgtlmoon]

It's not possible that the app only printed one line of output for 3 days, I need complete log data

And also, are you running this on your own system or is it some positive system like cloudron?

And what operating system?

[dgtlmoon]

I'm going to leave this in discussions because there's not enough information for the issue queue

• I need more complete log data on the hour (attach as .txt)
• And also, are you running this on your own system or is it some positive system like cloudron?
• And what operating system?
• Any other information like your timezone settings from /settings#timedate add a screenshot
• full screenshot of the scheduler area - you missed critical information like the actual timezone and time its reporting

[dgtlmoon]

Hello I leave it here until i get more information otherwise i cannot continue

[dgtlmoon]

@allddd HUGE apologies! please try 0.50.39 when its released in 15 minutes https://github.com/dgtlmoon/changedetection.io/actions/runs/19044380584

[chimpboy]

Thank you. I thought I'd messed something up - schedules stopped working last week.

[dgtlmoon]

@chimpboy all OK now on latest release?

[chimpboy]

Yes, working as it should. Thanks.

[allddd]

@dgtlmoon no worries :) sorry for the lack of info, I removed most of the details to anonymize the report.
I updated the instance and will check tomorrow to see if the issue persists.

[dgtlmoon]

please do <3

[allddd]

Can confirm it's working now. Thanks!