Error: Table 't_GQN5U5J7R7IV' Column Limit Reached

Taylor R. · 2024-01-30 14:20:38.356059+00

Got an error. Table 't_GQN5U5J7R7IV' cannot create new attribute due to column limit Disregard

Error: Table 't_GQN5U5J7R7IV' Column Limit Reached | Clay

12 comments

· Sorted by Oldest

Taylor R.
·
·
https://app.clay.com/workspaces/210079/tables/t_GQN5U5J7R7IV/views/gv_6rjq6H6OMuKR##
Clay Team
APP
·
·
Hey Taylor, thanks for reaching out!
Taylor R.
·
·
Hey- I'm struggling to test a few things
Clay Team
APP
·
·
Yep, based on that message it appears you reached the column limit for that table. Current limits are 50k rows and 70 columns per table.
Taylor R.
·
·
I have been adding and thinking I was removing the waterfall company email enrichment
Taylor R.
·
·
I have eliminated all the waterfall enrichments that I added previously. If I want to test 1 row at a time instead of the first 10, why is it not giving me a validated work email?
Taylor R.
·
·
Also- is it possible to sit with someone for a few minutes... I realize you guys probably have a lot going on, but there's a few particular use cases I just need a little help work through. I promise I'm not here to waste your time. This is me: https://www.linkedin.com/in/taylorryan/
Taylor R.
·
·
Would be really helpful to run through a few use-cases
Taylor R.
·
·
I've written a few questions related to deduping results and and removing general inbox emails....
Clay Team
APP
·
·
Ah, yup, just noticed that you removed some. About the email waterfall, I'll provide an explanation and video of what's going on but in essence, we don't control what each data provider returns so some emails could be deemed invalid by the validation tool
Clay Team
APP
·
·
The waterfall gives you the option to add a validation provider to check results from each email finder. When the validation tool determines the email is invalid, the next email finder tries to find a new one, but if it finds the same email as the previous column it won't try to validate it again because it already tried to validate once before, and this could result in no final output because none were valid.We automatically hide validation columns helping keep tables clean and that's why it's not evident at first glance. Let me know if you still have any questions though!Example and explanation: https://www.loom.com/share/e79acd92841a4706b1710c4ce1bddaa4
Clay Team
APP
·
·
I'll DM you the link instead, to find some time.

Taylor R.
·
·
https://app.clay.com/workspaces/210079/tables/t_GQN5U5J7R7IV/views/gv_6rjq6H6OMuKR##
Clay Team
APP
·
·
Hey Taylor, thanks for reaching out!
Taylor R.
·
·
Hey- I'm struggling to test a few things
Clay Team
APP
·
·
Yep, based on that message it appears you reached the column limit for that table. Current limits are 50k rows and 70 columns per table.
Taylor R.
·
·
I have been adding and thinking I was removing the waterfall company email enrichment
Taylor R.
·
·
I have eliminated all the waterfall enrichments that I added previously. If I want to test 1 row at a time instead of the first 10, why is it not giving me a validated work email?
Taylor R.
·
·
Also- is it possible to sit with someone for a few minutes... I realize you guys probably have a lot going on, but there's a few particular use cases I just need a little help work through. I promise I'm not here to waste your time. This is me: https://www.linkedin.com/in/taylorryan/
Taylor R.
·
·
Would be really helpful to run through a few use-cases
Taylor R.
·
·
I've written a few questions related to deduping results and and removing general inbox emails....
Clay Team
APP
·
·
Ah, yup, just noticed that you removed some. About the email waterfall, I'll provide an explanation and video of what's going on but in essence, we don't control what each data provider returns so some emails could be deemed invalid by the validation tool
Clay Team
APP
·
·
The waterfall gives you the option to add a validation provider to check results from each email finder. When the validation tool determines the email is invalid, the next email finder tries to find a new one, but if it finds the same email as the previous column it won't try to validate it again because it already tried to validate once before, and this could result in no final output because none were valid.We automatically hide validation columns helping keep tables clean and that's why it's not evident at first glance. Let me know if you still have any questions though!Example and explanation: https://www.loom.com/share/e79acd92841a4706b1710c4ce1bddaa4
Clay Team
APP
·
·
I'll DM you the link instead, to find some time.