Feed updates are paused permanently when there's a network error
Categories
(MailNews Core :: Feed Reader, defect)
Tracking
(Not tracked)
People
(Reporter: neikokz+mozbz, Unassigned)
References
Details
When a feed fails to download because of a network error, updates for said feed are paused seemingly forever. I don't think that behaviour is appropriate. I believe the feed should continue being fetched at the configured intervals.
The existing behavior is entirely intentional. Any manual check will try again, and it will be tried again after a restart. But it will not blindly keep retrying in the automatic polling cycle.
No chance an option can be added to fix this? Imagine if we applied this to email, and we stopped checking for email if there's a single network error until the client is restarted. It is simply inappropriate.
|
||
Comment 3•6 years ago
|
||
Do we differentiate between error codes? Agreed if it's 404, but other random errors (and no error code) should not cause permanent failure.
|
||
Updated•4 years ago
|
|
||
Updated•3 years ago
|
|
||
Comment 4•1 year ago
|
||
I systematically have all feeds paused if my PC wakes up from sleep. Presumably Thurderbird is checking the feeds before the network comes back up.
I think if there is a HTTP 404 or (especially) HTTP 410 then the feeds should be paused, but if the network is unreachable it is much more unclear, it is not that uncommon for networks to temporarily disconnect. Or if you're on something like a metered 5G network you may just have the internet off.
Description
•