Hi Irene,
Thank you for reaching out, and for the detailed explanation, it really helps.
Based on what you described, this may be related to one or more sources encountering errors during the automatic update process. When a source runs into an issue, it will usually show a “!” icon next to it under Aggregator → Sources. If a source keeps failing, it can sometimes interrupt or slow down the automatic updates for the other sources as well.
Since you mentioned that manually clicking Fetch works, this suggests that the feeds themselves are still accessible, but the automated process may be getting affected by one or more problematic sources.
Could you please try the following?
- Go to Aggregator → Sources in your dashboard
- Check if any sources show a “!” icon (this indicates an error)
- If you find any, try pausing those sources temporarily
- Then wait for the next automatic update cycle and see if the other feeds resume updating normally
This will help us narrow down whether a specific source is causing the disruption.
Please let us know how that goes, and we’ll be happy to assist further if needed.
Hi,
Thanks for your response.
I’ve deleted or paused the blogs that were not updating.
I have deleted the plugin ‘Cron Jobs’, to see if that solves the problem.
Still investigating however…
As ever,
Irene
Hi Irene,
Thank you for the update.
At this stage, continuing to monitor the behavior is the right approach. If the automatic updates still do not resume consistently, please let us know.
We’ll be happy to continue investigating with you if needed.
@hendcorp :
I have deleted – also – the older items that are no longer updating.
Strangely, when people publish after 10PM the webloggerlijst.nl presents the next day date. (So when still published on April 7, it shows April 8)… Bug??
As ever,
Irene
And I have rolled back to v4
And now I’m back to v5 and everything runs smoothly.
Could it be that I switched off the ‘state’ the updates did not work any longer??
Hi Irene,
Thank you for the update, I’m really glad to hear that everything is running smoothly again on v5 🙂
It’s possible that switching between versions helped reset certain settings or processes behind the scenes. Additionally, we’ve included a few improvements to the migration handler in the latest version of Aggregator, which may have contributed to resolving the issue.
At this point, since things are working as expected again, I’d recommend continuing to monitor the updates over the next few days. If anything unusual comes up, please don’t hesitate to let us know and we’ll be happy to take a closer look.
Thanks again for your patience throughout this!
