Quota exceeded not handled
speedmann opened this issue · comments
⚠️ Check for existing issues before proceeding. ⚠️
- I have searched the existing issues, and there is no existing issue for my problem
Where are you using SuperAGI?
Linux
Which branch of SuperAGI are you using?
Main
Do you use OpenAI GPT-3.5 or GPT-4?
GPT-4
Which area covers your issue best?
Logging
Describe your issue.
I ran out of quota on my openai account and the agent kept trying to do the same thing in a loop over and over again.
How to replicate your Issue?
Have auto re-charge disabled on openAI accoint and have $0 balance and try to run any agent.
Upload Error Log Content
superagi-celery-1 | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] error_code=insufficient_quota error_message='You exceeded your current quota, please check your plan and billing details.' error_param=None error_type=insufficient_quota message='OpenAI API error received' stream_error=False
superagi-celery-1 | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/llms/openai.py:82] - OpenAi RateLimitError:
superagi-celery-1 | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] OpenAi RateLimitError:
superagi-celery-1 | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/llms/openai.py:82] - You exceeded your current quota, please check your plan and billing details.
superagi-celery-1 | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] You exceeded your current quota, please check your plan and billing details.
superagi-celery-1 | 2023-09-23 21:31:51 UTC - Super AGI - INFO - [/app/superagi/jobs/agent_executor.py:95] - Exception in executing the step: Failed to get response from llm
superagi-celery-1 | [2023-09-23 21:31:51,018: INFO/ForkPoolWorker-8] Exception in executing the step: Failed to get response from llm
superagi-celery-1 | [2023-09-23 21:31:51,020: INFO/MainProcess] Task execute_agent[0931cc4d-da39-4e36-b7b6-9aeb5b0c48aa] received
superagi-celery-1 | [2023-09-23 21:31:51,021: INFO/ForkPoolWorker-8] Task execute_agent[43c135c0-209d-41c8-8f2f-622ff660ee42] succeeded in 0.28975934800018877s: None
@speedmann, thanks for flagging this issue, we're fixing it!
