VERY intermittent yes.
Same here, GTP3 being a crucial part of my app, this will hopefully get fixed soon ![]()
Same here - clearly an issue. Please fix asap
Please fix this, I’m tired of sending emails to our users saying that our servers are overloaded when they’re not…
Same here, really annoying. Haveing a paid account and maybe sending 1 or 2 requests per minute for testing
Sometimes its running, sometimes it fails
You can add a test condition to your code and when the API is overloaded and fails, you can wait a few “random” seconds and resubmit.
It’s just a few lines of code. Of course, you will need to parse the API error messages and make sure it is a type of “overloading” issue, testing it, etc.
Maybe on every retry send an email to OpenAI support. Complaining haha ![]()
It feels a bit wrong to implement a retry-mechanism when the API returns “too many requests”
but I guess it will have to do for now.
Make sure your account is attached to a card even if youre under the $18
I implemented retry logic in my code with a random time out and varied the davinci model, but still getting the too many requests. are you a paid account?
Similar issue here. Any requests through the API gives the same 429 error. Even sending a single request with the API playground gives the ‘You’ve reached your usage limit.’ error. I have a paid account, and am not even close to the usage limit. I tried creating a second account with a new email, credit card and phone number and got the same error.
Anyone else completely locked out of the API?
Just getting set up so could be a noob issue but my initial request are returning status code 429.
If you search the forum (the big magnifying glass icon on the top right of every page), you will see that this topic has been discussed to death already:
That tends to happen when an issue keeps getting
worse instead of getting resolved
You’re not alone. Nowhere near usage limits, and OpenAI is charging us for PROMPT tokens even when completions fail. Ridiculous.
Ok. It looks as though we are never going to get a response from support. I’m sure they are overwhelmed, but this issue is very pervasive. So I have some questions if anyone would be willing to answer:
- How long have you been using the API?
- During that time frame were you ever successful getting a completion to work?
- If yes, when did it stop working for you?
- When sending requests today, for your particular account, are any requests getting through or none?
- Which model(s) are you having difficulty with (Please list models and their success/failure stats)?
- Are you a free account or paid account?
- If paid, which account type did you sign up for?
Perhaps if each user lists their specific issues, when a support resource is able to look at the stats they will be able to more easily isolate the issue.
My answers:
- I have been attempting to use the API for about 1 month.
- I have never been successful getting a completion through with nextjs code or Postman. I’ve changed models, retry logic, new tokens, upgraded to a paid account and have never received a 200 for a completion request
- It has never worked
- None
- I’m rotating through text-davinci-001 - 003
- Paid (which is kind of a kick in the cohones)
- ChatGPT Plus
5 weeks, give or take.
Yes, my completion success rate is over 99%. The only problem I have ever had was when I called the API in a loop without any delay. Now I always add delay in my loops which call the API.
The API works fine for me, especially considering the API is considered a “research beta”, to be honest, and the API has never stopped working but it has failed a handful of time due to system loading issues (expected during such media hype and exponential growth period in a beta release). Very sorry to hear to you are having this problem, and I hope things improve for everyone soon.
I have sent many requests today with 100% completion rate. Yesterday, I sent many fine-tunings, completions and embedding request without any noticeable issues, except of course fine-tuning is, understandable, a slow process.
None.
I am using credits generously granted to me by OpenAI (Thanks OpenAI); and am reluctant to move to a fully paid account until the growing pains are better. My experience over the years in tech is that if you are “too early an adopter” you put yourself at risk of being disappointed and frustrated, so I practice “late, early adoption” or even “delayed adoption” depending on the situation. I try to keep my expectations low with beta releases and generally try to participate in helping debug the system, patiently.
N/A
My issue is resolved.
The error for me exists between the keyboard and the chair.
I was getting the 429 errors with my free usage. My completions never worked.
In error, in order to fix, I signed up for a paid account. The problem was I signed up for the Plus account which gave me better access through the website thinking it was also API related. Tonight I decided to sign up for pay as you go and I am now receiving completions.
I still don’t understand why my free usage was at 0 use and receiving 429s, but once I signed up for pay as you go, I started to receive responses.
So in my case, free usage aside, I’ve corrected with pay as you go. I realize that doesn’t help the people who are using the free type, but I thought I would fall on my sword for possibly someone else’s benefit.
@crgmonroe you mentioned you were using chatgpt pro
If you are using the API with that, it’s not a surprise you are having problems.
There is no API for chatgpt and openai are actively blocking access for apis as it is against their terms of service
Hahaha.
Yes, I have noticed that a lot here, but never say anything in reply, but you @crgmonroe have made me smile a bit bigger this morning.
We have no short of people here tossing rocks and chunking spears at OpenAI who fit into exactly what you have said in your post, @crgmonroe
Thank you for that reply!
You made my day and restored a bit of my faith in humanity with that single line!
![]()
Thanks Ruby.
My motto in life is “no pride.” Raise the ship.
I’m glad I was able to bring a smile to your face. ![]()
Thanks for your engagement in this thread.
