Error: Cannot Read Properties of Undefined in ChatGPT AI Prompt

Joel K. · 2024-12-16 14:15:05.804892+00

Hi all. Getting _Cannot read properties of undefined (reading 'includes')_ error when trying to run an ChatGPT AI prompt.

Error: Cannot Read Properties of Undefined in ChatGPT AI Prompt | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
This error typically occurs when the prompt structure isn't properly formatted. To resolve it, follow these prompt engineering best practices: 1. Always start with a clear system prompt that provides context and outlines your goal. 2. Structure your instructions in a step-by-step format to avoid undefined references. 3. Be explicit about your desired output format and include all necessary parameters.If you continue experiencing issues, please ask for human support to review your specific prompt structure and help identify the exact cause of the error. Sources: Prompt Engineering Crash Course [Limitless Research] - Clay University Prompt Engineering Crash Course [Clay 101] - Clay University
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!
Mark L.
·
·
Joel, thanks for raising this. Could you let me know which table(s) you're working on where you see this error? I'd love to look into it with you.
Joel K.
·
·
No problem. Here is the table: https://app.clay.com/workspaces/239552/tables/t_toKHF8kawQd5/views/gv_iEDTDq3gVCeU
Mark L.
·
·
Joel, looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. I'll follow up here as soon as we know more. In the meantime, I've duplicated the column – "Clay Test – LinkedIn Profile URL" – and I can see that one completed as expected. I'm not sure what cause the original to hiccup, but hopefully relying on the new one can help you take next steps. More to come!
Mark L.
·
·
Joel, just a quick follow-up to note that this issue has been resolved. I re-ran a cell in the "LinkedIn Profile URL" column where we originally saw this, and got the expected result. That should take care of everything here, so I'll tentatively go ahead and close this. If you see any new issues, though, please don't hesitate to reach out. :)
Channeled
APP
·
·
Hi Joel K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
This error typically occurs when the prompt structure isn't properly formatted. To resolve it, follow these prompt engineering best practices: 1. Always start with a clear system prompt that provides context and outlines your goal. 2. Structure your instructions in a step-by-step format to avoid undefined references. 3. Be explicit about your desired output format and include all necessary parameters.If you continue experiencing issues, please ask for human support to review your specific prompt structure and help identify the exact cause of the error. Sources: Prompt Engineering Crash Course [Limitless Research] - Clay University Prompt Engineering Crash Course [Clay 101] - Clay University
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!
Mark L.
·
·
Joel, thanks for raising this. Could you let me know which table(s) you're working on where you see this error? I'd love to look into it with you.
Joel K.
·
·
No problem. Here is the table: https://app.clay.com/workspaces/239552/tables/t_toKHF8kawQd5/views/gv_iEDTDq3gVCeU
Mark L.
·
·
Joel, looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. I'll follow up here as soon as we know more. In the meantime, I've duplicated the column – "Clay Test – LinkedIn Profile URL" – and I can see that one completed as expected. I'm not sure what cause the original to hiccup, but hopefully relying on the new one can help you take next steps. More to come!
Mark L.
·
·
Joel, just a quick follow-up to note that this issue has been resolved. I re-ran a cell in the "LinkedIn Profile URL" column where we originally saw this, and got the expected result. That should take care of everything here, so I'll tentatively go ahead and close this. If you see any new issues, though, please don't hesitate to reach out. :)
Channeled
APP
·
·
Hi Joel K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: