OpenAI Key Error: Functionality Issues Reported

Vik

We got error just running OpenAI with our own key. 2 mins ago everything worked fine. No explanation behind

18 comments

Channeled
APP
·
·
There are a few possible reasons for this sudden error: 1. Your OpenAI API key might have expired or been invalidated. You can verify and get a new key at OpenAI API Keys. 2. You may have reached your OpenAI account's usage limits. Check your current usage and limits at OpenAI Usage and OpenAI Limits. 3. Your OpenAI account tier might not meet Clay's requirements (30,000 TPM for ChatGPT columns, 450,000 TPM for Claygent). If the issue persists, please share the exact error message you're seeing.
Vik
·
·
https://app.clay.com/workspaces/43738/workbooks/wb_0sww587ZRvbKJRV5cCm/tables/t_0sww58kiacVa8ApheAh/views/gv_0sww58kw6tU9EYDanRN
Vik
·
·
When I switch to Clayagent (Web Research) - it works
Vik
·
·
When I switch to Content Creation, Manipulation - it gives me Error with 0 explanation behind
Vik
·
·
Yeah I try other columns - OpenAI simply doesn't work
Vik
·
·
I mean, Content Creation, Manipulation does not work -always Error for no reason
Vik
·
·
I can assure we have money on OpenAI account -> simply that switch I mentioned above generates an error
Stefano
·
·
Hi Viktor, thank you for reaching out. I believe we might have a bug on our hands, but I will have to further inspect this issue to make sure about this. Thank you for your patience as we get to the bottom of this.
Vik
·
·
got it - thank you
Mikhail
·
·
Same problem as Vik, following this thread
1
Jenna M.
·
·
Same problem here, using our own API key or Clay's
1
Stefano
·
·
Viktor - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Mosie M.
·
·
I have the same issue
Mosie M.
·
·
Stefano any update on this?
Stefano
·
·
Hi, it should be working fine now.
1
LuisArturo
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
Vik
·
·
hello?
LuisArturo
·
·
Hey there Viktor sorry for the delay here, which table is this in, did not see it in the table linked above.