Feeds not updating regularly cron works fine...

[adegans]

• [x ] I have read the CONTRIBUTING.md and followed the provided tips
• [ x] I accept that the issue will be closed without comment if I do not check here
• [x ] I accept that the issue will be closed without comment if I do not fill out all items in the issue template.

Explain the Problem

Not a bug perse - Perhaps a config issue. Not sure yet. Need some advise/ideas first.

I Installed Nextcloud news yesterday - Default settings.
Imported my feeds (20 or so) from a opml file all previous items got loaded fine. All shows up as normal.

Marked all as read and went to bed.

This morning I open NextNews in iPad and have a few new items, latest item from 7:44 this morning. I checked around 11am.
Same on web UI and Lire (MacOS). But in Netnewswire which loads feeds independent there are newer items on the same feeds.
To 'force' the settings I changed the interval to 1800, it said saved.

Now again 6 hours later still no updates in nextcloud news - Yet NNW updates just fine every hour.

I see no errors or warnings in logs - It's as if the update job simply doesn't work or isn't scheduled.

So it would seem NC News updated once or twice to get the morning items and then stopped.

Everything else seems to work fine - Other cron jobs in NC are working fine according to the Settings > Basic page.

Steps to Reproduce

Explain what you did to encounter the issue

1. Have the plugin active and wait

System Information

• News app version: 18.1.1
• Nextcloud version: 24.0.3
• Cron type: (system cron/python updater/...) system via crontab - Works for everythign else.
• PHP version: 7.4.x
• Database and version: MySQL (mariadb) 8.something
• Browser and version: Safari Macos, Nextnews (iOS), Lire (macOS), Nextcloud News (Android)
• OS and version: Macos Monterey, Android 12, ipadOS 15

Contents of nextcloud/data/nextcloud.log

Nothing in the nextcloud.log mentioning news or feed failures or anything like that - Just a ton of Geoblocker stuff and suspicious login nonsense about untrained models.

[Grotax]

If there are no errors in the log it's most likely that you (or some software) accidently interrupted the news update job, by killing the PHP session.

That will lead Nextcloud into the dilema that the job is already marked as running but never finished in any way.

Nextcloud will reset and start the job again after 12h if I'm not wrong.

This can be especially painful if you have backup system in place that kills PHP to make a "clean backup". For example every night.

Changing that number will only take affect after the next scheduled run and not change it immediately.

[Emporea]

You could manually reset the job in the database.

In the table "oc_jobs", row "NewsUpdater" set the column "reserved_at" to 0.