You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are interested into the same feature.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using:
3.15.3
Is your feature request related to a problem? Please describe.
When an error causes a sync to fail and is not a one-off issue, the client will keep trying to sync and keep failing, creating an error notification for every single attempt. One notification every few seconds, sometimes faster than the timer for the notifications to disappear.
It's effectively a constant stream of messages where no information gets added that I didn't already get from the first one.
Describe the solution you'd like
A system like an exponential backoff function, where error messages of the same type get a shared timer that keeps increasing whenever it fires and decays when not.
E.g. after the same error message was shown two or three times, it will be suppressed for a minute. If it fires again after that minute, it gets suppressed for ten minutes. If it gets suppressed again, it gets an even higher timer, and so on. If the error message stops, the corresponding timer slowly decays. If it fires again before the timer reached zero, it gets increased again.
Describe alternatives you've considered
Nothing comes to mind that would allow me to temporarily disable notifications just this one type of notification.
Additional context
The text was updated successfully, but these errors were encountered:
How to use GitHub
Feature request
Which Nextcloud Version are you currently using:
3.15.3
Is your feature request related to a problem? Please describe.
When an error causes a sync to fail and is not a one-off issue, the client will keep trying to sync and keep failing, creating an error notification for every single attempt. One notification every few seconds, sometimes faster than the timer for the notifications to disappear.
It's effectively a constant stream of messages where no information gets added that I didn't already get from the first one.
Describe the solution you'd like
A system like an exponential backoff function, where error messages of the same type get a shared timer that keeps increasing whenever it fires and decays when not.
E.g. after the same error message was shown two or three times, it will be suppressed for a minute. If it fires again after that minute, it gets suppressed for ten minutes. If it gets suppressed again, it gets an even higher timer, and so on. If the error message stops, the corresponding timer slowly decays. If it fires again before the timer reached zero, it gets increased again.
Describe alternatives you've considered
Nothing comes to mind that would allow me to temporarily disable notifications just this one type of notification.
Additional context
The text was updated successfully, but these errors were encountered: