Issue with Lookup Single Row Function in Clay Workspace

Vedarsha Chellan · 2024-09-05 20:43:30.217056+00

Hi, having an issue with the Lookup Single Row in Other Table function. I imported a list of company domains from Phantom Buster to a Clay workspace - link attached: and want to use the Lookup Single Row in Other Table function to link company names and domains according to the attached image. The LookUp function does not work. I created a new LookUp Single Row column in this workspace (column 34). The run still shows the same error message. Please let me know how I can resolve this issue.

Issue with Lookup Single Row Function in Clay Workspace | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bo (Clay)
·
·
Hey, thanks for reaching out! 😊 I managed to fix the issue by: 1. Re-authenticating the Clay Table. 2. Adding the correct table (not the copy). 3. Re-running it. You can check it out in this view: Clay Table View. Let me know if you need anything else! 👍
Vedarsha Chellan
·
·
Hi Bo, thank you for the assistance. The error only occurs from row 2075. I've confirmed that this error with the "lookup single row in other table" function still occurs from row 2075 in the table attached in your response as well. It only works in column 34 from row 1 to row 2073.
Vedarsha Chellan
·
·
I attached a video, hope it will help to understand the issue.https://www.loom.com/share/8320930757d64f6d9d30e49726e35432?sid=5822181c-1b21-4d56-be36-9b37bea4b0ae This same error occurs in column 34 as well from row 2075.
Bruno (Clay)
·
·
Hi Vedarsha, thanks for reaching out. Can you confirm that the new leads you added to the table are actually present in the table you're looking them up in? If you select row 2075, for example and then go to your Phantombuster source table - are those leads present in that table?
Vedarsha Chellan
·
·
I've added another video, hope that's okay https://www.loom.com/share/0346ab42069446678c6dcd6b8f8a5421?sid=6c158cf7-37b5-413f-94ae-3ab02994b513
Vedarsha Chellan
·
·
This workflow been successful previously to assign company domains, but for some reason is not working for the new leads
Tanvi (Clay)
·
·
Hi Vedarsha, thanks for sharing this additional context. It looks like this could be a bug on our end, I have flagged this for our engineering team to take a closer look and will get back to you once I know more.
Tanvi (Clay)
·
·
Hey Vedarsha, I just checked with my team and this is not a bug. Sometimes records have 'ghost' or 'undetectable space' characters. I used a formula to trim them in a new column and now it works. Please try running the rest of your table and let me know if you run into any other issues! https://downloads.intercomcdn.com/i/o/1171651231/263577f8d6387f86fed38fd8/image+%283%29.png?expires=1725660900&signature=c3f30b8f68df4c75bf5fc0e1b748ba8fd1a43bb05cdbddeb6af5bd304e7d3aac&req=dSEgF897nINcWPMW1HO4zaLCMhF%2BAiXIborw8VQuzu1T3yDM1smCUl4kfdpJ%0AhHDs%0A
Channeled
APP
·
·
Hi Vedarsha Chellan! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Bo (Clay)
·
·
Hey, thanks for reaching out! 😊 I managed to fix the issue by: 1. Re-authenticating the Clay Table. 2. Adding the correct table (not the copy). 3. Re-running it. You can check it out in this view: Clay Table View. Let me know if you need anything else! 👍
Vedarsha Chellan
·
·
Hi Bo, thank you for the assistance. The error only occurs from row 2075. I've confirmed that this error with the "lookup single row in other table" function still occurs from row 2075 in the table attached in your response as well. It only works in column 34 from row 1 to row 2073.
Vedarsha Chellan
·
·
I attached a video, hope it will help to understand the issue.https://www.loom.com/share/8320930757d64f6d9d30e49726e35432?sid=5822181c-1b21-4d56-be36-9b37bea4b0ae This same error occurs in column 34 as well from row 2075.
Bruno (Clay)
·
·
Hi Vedarsha, thanks for reaching out. Can you confirm that the new leads you added to the table are actually present in the table you're looking them up in? If you select row 2075, for example and then go to your Phantombuster source table - are those leads present in that table?
Vedarsha Chellan
·
·
I've added another video, hope that's okay https://www.loom.com/share/0346ab42069446678c6dcd6b8f8a5421?sid=6c158cf7-37b5-413f-94ae-3ab02994b513
Vedarsha Chellan
·
·
This workflow been successful previously to assign company domains, but for some reason is not working for the new leads
Tanvi (Clay)
·
·
Hi Vedarsha, thanks for sharing this additional context. It looks like this could be a bug on our end, I have flagged this for our engineering team to take a closer look and will get back to you once I know more.
Tanvi (Clay)
·
·
Hey Vedarsha, I just checked with my team and this is not a bug. Sometimes records have 'ghost' or 'undetectable space' characters. I used a formula to trim them in a new column and now it works. Please try running the rest of your table and let me know if you run into any other issues! https://downloads.intercomcdn.com/i/o/1171651231/263577f8d6387f86fed38fd8/image+%283%29.png?expires=1725660900&signature=c3f30b8f68df4c75bf5fc0e1b748ba8fd1a43bb05cdbddeb6af5bd304e7d3aac&req=dSEgF897nINcWPMW1HO4zaLCMhF%2BAiXIborw8VQuzu1T3yDM1smCUl4kfdpJ%0AhHDs%0A
Channeled
APP
·
·
Hi Vedarsha Chellan! This thread was recently closed by our Support team. If you have a moment, please share your feedback: