Issue with Incomplete Lookup Records Enrichment for Campaign Processing | Clay

Issue with Incomplete Lookup Records Enrichment for Campaign Processing

Hello team, I am facing an issue with Lookup records enrichment. it is fetching only partial information for the records. I am looking up people records for a company and apart from the first record, all other records are missing some fields. One of the missing field is email validation status. It is not being fetched for all records even though it is properly populated for all. This is a critical field in the downstream processing of records for campaigns. Table link: https://app.clay.com/workspaces/39601/tables/t_RTENUvUyJPGx/views/gv_VF2EiiaJA2aC

14 comments

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!
Parul R.
·
·
Bo (.
·
·
Hey Parul, This issue is similar to the one explained here: Loom Video.The reason you’re seeing this is that the Integration column only displays partial results of the text. To view the full text, you’ll need to export the results as a column, which will allow the lookup to access the complete data. Hope this helps, and let me know if you have any more questions!
Parul R.
·
·
Bo (. Thanks for responding. The issues are not the same. The issue which I am facing involves missing column variables in the lookup results. When these variables are written in the next table, the column values are empty because they are not lookedup from the source table. The problem is in lookup logic. Also, I can’t export and write individual record in the same table as it is multiple record lookup which requires a different table to export results and column values are missing in that table as well. Please look at the Clay table which I have shared above. Also, this is a time critical issue as my client’s campaigns are paused due to this. Can you please check this?
Parul R.
·
·
Bo (. I have recorded the erroneous behaviour of the lookup column in this loom video. Currently, I am applying a workaround (as explained in the attached loom video) to fix the error but this is recurring issue so a proper solution is needed and will be appreciated. Loom video: https://www.loom.com/share/0b4d984674a14e28a4bf89fce0afc37f?sid=e94adf9f-0ad6-451f-bce0-0c949afeb353
Daniela D.
·
·
Hey Parul! Thanks for reaching out. Apologies for the confusion. I ran a number of checks in your workspace. It's not entirely clear why those fields didn't update during the initial run. For context, this usually happens if certain fields in the other table have not yet populated in the source table. We also noticed that contacts that are not marked as "True" will also get pulled via Lookup if they have a matching company ID. In those instances, the column value will not show true. However, I ran a few more tests to recreate that workflow and can confirm the cells now update correctly for records that are "True"✅. It may have been a temporary glitch at the time, but totally understand how frustrating that can be. Can you let us know if you see this happen again? I'll be happy to troubleshoot further.
Channeled
APP
·
·
Hi Parul R.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Parul R.
·
·
Daniela D. The issue is occurring again. It is becoming troublesome for the client. Can you please look into it and suggest a resolution asap?
Parul R.
·
·
Table link: https://app.clay.com/workspaces/39601/tables/t_RTENUvUyJPGx/views/gv_VF2EiiaJA2aC
Tanvi R.
·
·
Hi Parul, thanks for reaching out! If you are still experiencing this issue it might be a bug related to the high record count you are importing. I've escalated this over to our engineering team and we'll let you know as soon as we know more!
Tanvi R.
·
·
Hey Parul, I just checked with my team and it looks like the records updated after the lookup already ran. Since it's not live sync, you'd have to re-run the cell to update it which should import the 'true' and other fields. I just tried to re-run the lookup cells but there's just too much data now that it couldn't hold it. Could you create a new lookup column and try running this? Let us know if all the fields are able to import successfully in the new column!
Bo (.
·
·
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 provide insight on expectations, issues like this may not be actioned for some weeks. This timeline is based on the team's current existing log of issues and upcoming feature releases which is subject to change. So what happens now? Now that your issue has been logged, I will wrap up this conversation. 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 Parul R.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: