AI Enrichment Error: Assistance Needed for Table URL Issue

Drake Thomsen · 2024-12-16 20:14:43.932595+00

I'm getting a weird error when trying to run an AI enrichment. Here's my table's URL:

AI Enrichment Error: Assistance Needed for Table URL Issue | Clay

9 comments

· Sorted by Oldest

Drake Thomsen
·
·
I removed all references to other cells and I'm still getting the same error
LuisArturo (Clay)
·
·
Hey there Drake thanks for reaching out, could you reenter all of the cell references so that I can check to see which one was shooting out the error. The error is being returned again because it is expecting there to be an input but there is none in the prompt.
Drake Thomsen
·
·
Huh... I re-entered the prompt and it executed just fine, but when I went to generate examples from previewing rows, I got the error again.
Loading attachments
LuisArturo (Clay)
·
·
I see thank you for sharing, I will bring this up with the team to see why this error is being outputted during the preview.
Drake Thomsen
·
·
Just tried a similar AI enrichment and had it work. I think the bug has something to do with how the enrichment saves the prompt and examples. I'll write a detailed bug report below
LuisArturo (Clay)
·
·
Thank you Drake
Drake Thomsen
·
·
Steps to reproduce the bug:
1.
Make sure you are using the GPT 4o model with a custom API key
2.
Select a Clay template that was saved with examples on another table
3.
Make any edits necessary to the template
4.
Click "Save" then "Save and don't run"
5.
Re-open the edit column box and remove any saved examples
6.
Attempt to create new examples by previewing
7.
Previewed rows will encounter the bug
Note:
If you delete the saved examples PRIOR to clicking "Save and Don't Run", generating examples from previewing rows will behave as expected.
Trying to generate examples without first clicking "Save and Don't Run" appears to send an empty prompt to the GPT 4o API
LuisArturo (Clay)
·
·
Thank you for this Drake will share this with the team.
Channeled
APP
·
·
Hi Drake Thomsen! This thread was recently closed by our Support team. If you have a moment, please share your feedback: