openclaw - 💡(How to fix) Fix UX: Improve user feedback for transient rate-limiting to prevent false-negative panic [1 participants]

Currently, the system displays a jarring red error message whenever a transient rate-limit (429) or timeout occurs. Distinguish between 'Fatal Error' (Red) and 'Transient/Retrying State' (Yellow/Warning). 2. When a transient error (e.g., 429) occurs, show a yellow warning (e.g., 'System busy, retrying... (1/3)'). 3. Only escalate to a 'Red/Fatal' error message if all retries are exhausted.

TL;DR

Implement a "Retrying" state in the UI to distinguish between fatal errors and transient errors, displaying a yellow warning for the latter.

Guidance

• Introduce a new UI state to handle transient errors (e.g., 429) and display a warning message indicating the system is retrying.
• Update the error handling logic to only display a red error message when all retries are exhausted.
• Consider adding a retry counter to the warning message to provide additional context to the user.
• Review the current retry mechanism to ensure it is properly handling transient errors and adjust the retry logic as needed.

Example

// Pseudocode example of the proposed solution
if (error_code == 429) {
  display_warning_message("System busy, retrying... (1/3)")
  retry_request()
} else if (all_retries_exhausted) {
  display_fatal_error_message("System error: all retries failed")
}

Notes

This solution assumes that the current retry mechanism is in place and functioning correctly. Additional logging or monitoring may be necessary to ensure the new UI state is properly handling transient errors.

Recommendation

Apply workaround: Implement the proposed solution to introduce a "Retrying" state in the UI, as it provides a clear distinction between fatal and transient errors, improving user experience and system clarity.