AutoGPT icon indicating copy to clipboard operation
AutoGPT copied to clipboard

[Builder] No Fallback or Timeout Handling for API Calls

Open andrewhooker2 opened this issue 1 year ago • 1 comments

⚠️ Search for existing issues first ⚠️

  • [X] I have searched the existing issues, and there is no existing issue for my problem

Which Operating System are you using?

MacOS

Which version of AutoGPT are you using?

Master (branch)

What LLM Provider do you use?

Other (detail in issue)

Which area covers your issue best?

Performance

What commit or version are you using?

b62c24dc77ba1aedd525d657424eb4ed0387b82f

Describe your issue.

Description

When making calls to the autogpt-server from our autogpt-builder, if there is an error or the server does not respond within a few seconds, the frontend currently has no fallback or timeout mechanism. This results in the user being left without any notification or resolution.

Steps to Reproduce

Open the application and navigate to a feature that makes a call to the autogpt-server. Simulate a server error or delay the server response beyond a few seconds. Observe the frontend behavior. Expected Behavior If the autogpt-server returns an error or does not respond within a few seconds, the frontend should:

Terminate the request.

Notify the user of the error or timeout. Actual Behavior The frontend has no fallback or timeout mechanism, leaving the user without any notification or resolution if the server has an error or delays in response.

Suggested Solution

Implement a fallback or timeout mechanism in the frontend to handle:

Termination of the request after a specified timeout period (e.g., 5 seconds). User notification indicating that an error occurred or the request timed out. NextJS handles fallback / error pages well leveraging the file name of error.tsx

Environment

Browser: Chrome Operating System: MacOS

Upload Activity Log Content

No response

Upload Error Log Content

No response

andrewhooker2 avatar Jul 26 '24 17:07 andrewhooker2

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

github-actions[bot] avatar Sep 17 '24 01:09 github-actions[bot]

This issue was closed automatically because it has been stale for 10 days with no activity.

github-actions[bot] avatar Sep 27 '24 01:09 github-actions[bot]