Glitch Detected in AI Column of Data: Sr/Mgr Workbook | Clay

Glitch Detected in AI Column of Data: Sr/Mgr Workbook

Hi, there appears to be a glitch in my "Short Company Name" AI column in the Data: Sr/Mgr workbook here: https://app.clay.com/workspaces/276109/workbooks/wb_0syo909yX24YFDjDdZR/tables/t_0szeoleNyWAJQ5qKvWS/views/gv_0szg6cg6AZnRkjhgdFr It has been loading since this morning, without any results. Can someone please take a look? Trying to ship these campaigns

7 comments

Clay
APP
·
·
Your AI column is likely stuck in a queued state. Try these solutions: Quick Fix: Click the column header and select Force Rerun Column to reset it. Alternative Method: 1. Click the column header 2. Hover over "Run column" 3. Select Force to jump start the column If Still Stuck: Try a hard refresh: ** Windows: Ctrl + Shift + R ** Mac: Cmd + Shift + R Last Resort: Create a new column by duplicating the current one, filter for rows where the original column "is empty," then run the AI on those rows. Use the "merge columns" feature to combine results. Performance issues can occur with larger tables, so the hard refresh often resolves loading delays.
Katie
·
·
I have already done this. And I just did it again, and it's not helping
Katie
·
·
2 tables:
1.
Data: Sr/Mgr, Column = "Short Company Name"
2.
Data: Sr/Mgr #2, Column = "Casual Company Name"
Both in this workbook: https://app.clay.com/workspaces/276109/workbooks/wb_0syo909yX24YFDjDdZR/tables/t_0szeoleNyWAJQ5qKvWS/views/gv_0szg6cg6AZnRkjhgdFr
Mark L.
·
·
Hey Katie, thanks for sharing this, and for the sharing the links (both times!). I'll have a quick look and report back shortly with some initial thoughts. Looking forward to working through it!
Katie
·
·
thanks Mark L.!
Mark L.
·
·
When I edit the 'Short/Casual Company Name' columns, I see an alert, and an error coming back from the OpenAI API:
(193 kB)
Mark L.
·
·
Looks like this is related to the limits of the plan, for that particular account. https://platform.openai.com/docs/guides/error-codes/api-errors Based on the details of their docs above, our best options would be one of... - contacting OpenAI to add budget/increase rate limits available, which is naturally out of our direct control - switching to a lower-cost model in Clay (success would still depend on available budget, and of course the quality of the results you'd get back) - switching to a Clay-managed key