Claygent Bug: Incorrect Output in Response Column for Prompts | Clay

Claygent Bug: Incorrect Output in Response Column for Prompts

Claygent Bug: I keep getting {"response":"(prompt response)","data_link":" In the response column for my prompts? as mentioned above it affects about 5 to 10 % of my output. I can definitely say that it is a new occurrence since the table is a template I have been using it for months without this issue. If i was to assume what could be wrong the integration seems to mistake that the output needs to be labeled in properties of "response" and "link" when in actuality that has already happened and its putting that in the "response" property. Here is a loom Here is the table

9 comments

Channeled
APP
·
·
This issue is likely related to the JSON output settings in your AI integration. When you're getting a response with {"response":"(prompt response)","data_link":""}, it means the system is treating the output as a JSON object when it shouldn't be.To resolve this, check your integration settings and make sure the "Return as JSON Object" option is disabled if you don't need structured JSON output.If you need to adjust the output format, you can modify this in the "Define column outputs" section, where you can specify how you want the AI's response to be mapped. By default, the field will return as Text unless another data type is specified. Sources: Use AI - Clay University ChatGPT: Generate text with OpenAI/GPT
Balsa K.
·
·
Not the case
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Aly H.
·
·
Curious about this as well as I ran into this issue with a bit of data yesterday. It was only a few rows out of hundreds but definitely weird to see.
Bruno R.
·
·
Hi Balsa, thank you for reaching out. I see what you mean—one row appears to be formatting the output in an unexpected way. This could be related to the model you're using. We recommend adding examples to your GPT column to help guide the output and refining your prompt using the "Help me" tool to better define the desired results. Let us know if you need further assistance!
Balsa K.
·
·
Hey Bruno R. if you check the table and prompt you will see plenty of examples I think 10. Then also I explicitly tell the model to not do that. Also as mentioned this is a template I'm running for 3 months now on 10s of thousands of rows and this started happening only now. About the time when you guys introduced the JSON schema in claygent. Now my opinion is that since the problem is litterly the model giving a JSON object with properties of response and link that something got messed up in the integration with that new update. What do you think?
Bruno R.
·
·
Upon further investigation, I believe our engineering team will take a look at this issue closer and determine what may be causing it, thank you for reporting this!! We will be in touch as soon as we have news on this.
Bruno R.
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
Channeled
APP
·
·
Hi Balsa K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: