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
Today some subscriptions may repeat failed sendings about 50+ times, because:
telegram bot blocked
slack channel archieved
wrong contact address
etc.
But some reasons is ok: timeouts or others (?), we need pass them.
This sending attempts generate unneccessary activity and trash collected at logs.
Possible way:
Add some euristic to check notification fail reasons and attempts count, and disable subscription automatically.
Add to admin page: enable/disable this feature and abillity to restore (enable all disabled) in case of fuckups.
Send banned count metric.
The text was updated successfully, but these errors were encountered:
Today some subscriptions may repeat failed sendings about 50+ times, because:
But some reasons is ok: timeouts or others (?), we need pass them.
This sending attempts generate unneccessary activity and trash collected at logs.
Possible way:
Add some euristic to check notification fail reasons and attempts count, and disable subscription automatically.
Add to admin page: enable/disable this feature and abillity to restore (enable all disabled) in case of fuckups.
Send banned count metric.
The text was updated successfully, but these errors were encountered: