openclaw - 💡(How to fix) Fix WebUI does not display error messages when model API calls fail (429, timeout) [1 participants]

From gateway log:

19:50:26 WARN rate_limit: 429 usage allocated quota exceeded. please try again later.
19:50:26 WARN embedded run failover decision: surface_error

TL;DR

Implement error handling in the WebUI frontend to catch and display model API errors.

Guidance

• Review the WebUI frontend code to identify where the model API response is being handled and add error handling for 429 quota exceeded, timeout, and network errors.
• Use the error messages from the gateway log (e.g., "429 usage allocated quota exceeded") to inform the user-friendly error messages displayed in the WebUI.
• Consider adding a retry mechanism with a delay to handle temporary errors like quota exceeded or network errors.
• Verify that the error handling is working correctly by simulating the model API errors (e.g., sending a request when the quota is exceeded) and checking that the expected error messages are displayed in the WebUI.

Example

// Pseudo-code example of error handling in WebUI frontend
fetchModelData()
  .catch(error => {
    if (error.status === 429) {
      displayErrorMessage("⚠️ API quota exceeded. Please try again later.");
    } else if (error.status === 504) {
      displayErrorMessage("⚠️ Request timed out. Please check your network connection.");
    } else {
      displayErrorMessage("⚠️ Model unavailable. Please try again later.");
    }
  });

Notes

The exact implementation of error handling will depend on the WebUI frontend framework and technology stack being used. This guidance assumes a JavaScript-based frontend, but the principles apply to other technologies as well.

Recommendation

Apply workaround: Implement error handling in the WebUI frontend to catch and display model API errors, as this will provide a better user experience and help diagnose issues.