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
Previously, chain synchronization failures would retry immediately
without any delay, which could lead to tight retry loops and high
CPU usage during failures.
This change introduces exponential backoff for transient
errors, starting at 2 seconds and doubling each time up to a maximum
of 300 seconds. Persistent errors also now delay retries by the
maximum backoff duration to prevent rapid loops while maintaining
eventual recovery.
Fixes#587
0 commit comments