Help Needed: Clay Table Lookup Function Truncating Data

Irina Cismas · 2025-07-17 14:05:31.215694+00

hi guys - I have this table : and when I use the function Lookup Multiple Rows in Other Table some information is not passed in full from the original table. It is truncated. So basically my opener_line column has truncate values. Can someone help me out with this issue?

Help Needed: Clay Table Lookup Function Truncating Data | Clay

9 comments

· Sorted by Oldest

Clay
APP
·
·
Data truncation in lookup columns can occur due to processing issues. Try these solutions: 1. Force rerun the column: Click the column header and select "Force Rerun Column" to reset it 2. Recreate the column: Delete the affected column, create a fresh one, and re-map your data 3. Check the limit setting: The Lookup Multiple Rows function has an optional "Limit" parameter that controls the maximum number of rows returned, which can affect response size If the column appears stuck on "queued," the Force Rerun option should resolve the processing issue and restore your full data.
Source: Lookup Rows | Documentation | Clay University
Clay
APP
·
·
Hello Irina! Thanks for reaching out! Taking a look now!
Irina Cismas
·
·
I did that but unfortunately Re-Run did not work, Recreating the column did not work - not sure how i can get the non truncate informaiton.
Clay
APP
·
·
Hey Irina! Thanks for reaching out. Just to confirm, by opener_line which of these do you mean?
(43 kB)
Just confirming to make sure we are aligned!
Clay
APP
·
·
I checked your main table and looks like you are referring to the Personalized Email Opener. Taking a look now
Irina Cismas
·
·
Both of them
Irina Cismas
·
·
Both of them are truncated
Clay
APP
·
·
Hey Irina! I found the underlying issue. The response column under the Personalised Email Opener was not pulled out as an independent column and hence was getting truncated. I added it as a separate column and performed the lookup again and it seems to work. You can see this in the Support View I created. The truncated column is colored red while the non truncated one is colored green. The solution here would be to pull it as a separate column and then perform the lookup to avoid truncation. I have created this Support View for the engineers since this is not intended behavior and I am escalating this to the engineering team. I would request to not make any changes in the Support View for the engineers to take a look!
Irina Cismas
·
·
sure thing

Clay
APP
·
·
Data truncation in lookup columns can occur due to processing issues. Try these solutions: 1. Force rerun the column: Click the column header and select "Force Rerun Column" to reset it 2. Recreate the column: Delete the affected column, create a fresh one, and re-map your data 3. Check the limit setting: The Lookup Multiple Rows function has an optional "Limit" parameter that controls the maximum number of rows returned, which can affect response size If the column appears stuck on "queued," the Force Rerun option should resolve the processing issue and restore your full data.
Source: Lookup Rows | Documentation | Clay University
Clay
APP
·
·
Hello Irina! Thanks for reaching out! Taking a look now!
Irina Cismas
·
·
I did that but unfortunately Re-Run did not work, Recreating the column did not work - not sure how i can get the non truncate informaiton.
Clay
APP
·
·
Hey Irina! Thanks for reaching out. Just to confirm, by opener_line which of these do you mean?
(43 kB)
Just confirming to make sure we are aligned!
Clay
APP
·
·
I checked your main table and looks like you are referring to the Personalized Email Opener. Taking a look now
Irina Cismas
·
·
Both of them
Irina Cismas
·
·
Both of them are truncated
Clay
APP
·
·
Hey Irina! I found the underlying issue. The response column under the Personalised Email Opener was not pulled out as an independent column and hence was getting truncated. I added it as a separate column and performed the lookup again and it seems to work. You can see this in the Support View I created. The truncated column is colored red while the non truncated one is colored green. The solution here would be to pull it as a separate column and then perform the lookup to avoid truncation. I have created this Support View for the engineers since this is not intended behavior and I am escalating this to the engineering team. I would request to not make any changes in the Support View for the engineers to take a look!
Irina Cismas
·
·
sure thing