-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Open
Description
When running base/node, some operations may retry automatically, but it is not always obvious when this happens or why. A bit more documentation would make node behavior easier to understand.
Problem Description
Operators may notice repeated log messages or delayed startup without knowing whether retries are happening or what is being retried. This can make troubleshooting feel confusing or unpredictable.
Expected Behavior
It should be easy to understand when retries occur, what triggers them, and how they affect startup or runtime behavior.
Proposed Solution
Add a short, easy-to-read documentation section that explains where retries happen in the node lifecycle, what kinds of failures trigger them, and how operators can reason about retry-related delays.
Metadata
Metadata
Assignees
Labels
No labels