@james It was a bug that has been fixed with 0.50.39.

In changelog I see "Bug fix - scheduler":

I just checked and scheduler is working again as expected.

Thanks for your patience @james

@james

is long time that I use that feature but it seems not working anymore since three or four days.

User guide is very very clear and before it was working according to configuration setup guide.

Giving a look on GitHub someone also had the same problem:
https://github.com/dgtlmoon/changedetection.io/issues/3593 but then discussion has been closed.

I don’t have any log and no any error showed.

Only when restarting instance, check works again.

To reproduce issue please try to copy my configuration above in screenshot.

• Time between check: 1 day
• Start at 4:00 AM for 8 hours.

Purpose of my configuration is to check changes only once on 4:00 AM from Tuesday to Friday.

Thanks

Setup Details

• Cloudron version: v8.3.2 (Ubuntu 24.04.2 LTS)
• app version: 0.50.38

Issue description

I enabled ’Settings > General > Use time scheduler’

Steps to reproduce the behavior

1. Go to 'Settings > General > Use time scheduler’
2. Configure ’Schedule time limits”
3. Scrape should start itself

Expected behavior

Scrape should be started but nothing happens. I think - but I’m not sure - this behavior is after 0.50.38 updates.

Screenshots

Additional context

If I restart instance, scrape will be started.

@dgtlmoon yes, I can understand how frustrating is.

Inaccurate reporting is a big waste of time, specially from developers side, and specially when those rules are written and are ignored by most...

Thanks for sharing your concerns, also will help this forum to have better reports and to be better place.

About negative feedback on this thread, please don’t care, I’m sorry if you got a different image about this place.

@dgtlmoon I wrote here about:

said in Mark Change Detection app as unstable?:

Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:

https://changedetection.io/CHANGELOG.txt

Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.

Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.

These problems affected instance from updates 0.50.28–0.50.38.

In the past, I've had similar issues with RSS generation, which is equally crucial for notifications.

Obviously, I don't want to dwell on the specific technical issues in this discussion, which are recommended - which, as noted, should be reported on your GitHub - but I did suggest marking the application as "unstable" due to these uncertainties in the releases which could disrupt the application's proper and normal functioning.

Everyone on this forum supports open source software and, eventually, recognizes its value by paying for licenses if with value. However, this doesn't mean we should necessarily settle.

I've been using Cloudron on various instances for over 5 years, with various paid licenses, and I've never never never had one problems with the stability of Cloudron or other apps. Also, amazing support, amazing forum, and a place where we try to help each other.

Therefore, I believe it's right to post observations when something isn't giving some troubles, always with the goal of improving and addressing each issue.

The request to delete the post also seems inappropriate: it's a form of censorship. On the contrary, it's important to explore these issues s community can make a more informed decision about whether and which solutions to use.

Obviously I disagree with the other forms of offense towards ChangeDetection.io and I thank you for the development work you are doing, as I immediately recognized in my first response post (where I wrote: As you can see, there is a lot of active development. Is very positive side, of course)

Thanks again for your efforts.

@nebulon “Unstable” can actually have many meanings, eg. from a purely technical or operational (user side) standpoint.

In my opinion, app instability should also be considered when the use of the app itself or specific functions may be subject to distruptions related to the development process.

However, I understand that, from a purely technical standpoint, the definition of instability is a bit more restrictive.

About next steps, I'll wait for the app to work properly again and disable automatic updates.

I'll then update only after reviewing the changelog and possibly testing that everything is working properly.

This way, I can revert immediately, not days later @robi

Thanks all for your comments and suggestions.

@james thanks for your answer.

Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:

https://changedetection.io/CHANGELOG.txt

Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.

Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.

That issues affected existing features, not new ones.

As you can see, there is a lot of active development.

Is very positive side, of course, as it means app is being actively maintained, but such frequent changes ca affect stability and break existing functionality.

Here updates activity:

https://git.cloudron.io/packages/changedetection-app/activity

In my opinion, level and frequency of updates makes app a bit unstable at the moment.

Hi all,

In last week Change Detection app is full of bugs and regressions: I don’t know if is the case or not to mark as unstable on the app store...

You can check changelogs.

If things will go like this, I’ve to find a valid alternative...

@girish You all are doing a great job

@philkunz yes, other users had different problems restoring backups (me too), that’s why I suggested to check other topics https://forum.cloudron.io/search?term=tarExtract&in=titlesposts.

Even because It seems that the source cause, in most scenarios, has not been identified, but in 9.x version of Cloudron situation it could be different and more reliable because of different backup health checks.

It could be interesting to know more about your setup so feel free to share here details useful for further analisys.

@philkunz please check old posts on this forum about this specific topic.

Also, it could be useful to know more about your setup...

Finally, an iOs client for Vikunja:

https://trykuna.app/

https://community.vikunja.io/t/i-created-a-ios-app-for-vikunja/4092

I had also problem with Todoist that was completely hosted on AWS... so this problem is affecting (or affected) also other services.

Thinking again to move to Vikunja even if missing different things...

@necrevistonnezr great advice. Thanks a lot

@james thanks again for your support. Following your advices, I confirm that everything is working now.

You can mark this topic as "solved”.

Thanks again James

@james Many thanks, I’ll give you a detailed feedback.

@james Thank’s a lot. I will follow your suggestions. About next updates, we will have to do the same?

@james thanks a lot for your patience

I’m not talking about chats but prompts... can you save a prompt to 0.5 and then update to 0.6?

@girish @nebulon hello, how I can get support for this problem?

Hi @joseph any news for this topic?