Error: Maximum Columns Reached in Table Despite Fewer Columns

Hi support! I am getting an error that says You have reached the maximum number of columns allowed (100 total), but I only have 19 columns in the table. Including a screenshot too

13 comments

Jill Y.
·
·
Clay
APP
·
·
The error message appears incorrect. Clay tables have a limit of 70 columns total, not 100. Of these 70 columns, up to 30 can be action/enrichment columns (or 40 if you use waterfalls). Since you only have 19 visible columns, the issue might be: • Hidden columns: Check if you have hidden columns by clicking the Columns button at the top of your table to see all columns. • Action column limit: If you're trying to add an enrichment column, you may have reached the 30 action column limit even though your total is under 70. The "100 total" in the error message seems to be a display bug, as our actual limit is 70 columns total.
Sources: Table columns | Documentation | Clay University Customize your table view | Documentation | Clay University
Jill Y.
·
·
Ok this leads to maybe another potential bug. When I deleted a "find work email" waterfall enrichment it left all the validate zerbounce columns as hidden. They did not get deleted in the waterfall delete
Clay
APP
·
·
This appears to be a bug. When you delete a waterfall, it should remove all associated columns including the hidden validation columns. The validation columns (like ZeroBounce) are hidden by default to keep your table tidy, but they exist behind the scenes as part of the waterfall process. To fix this issue: 1. Delete the hidden columns manually: Click on the Columns button at the top of your table to see all columns, then delete the remaining ZeroBounce validation columns individually. 2. Check for other hidden provider columns: The waterfall may have left other hidden provider columns that also need manual deletion. This behavior where validation columns remain after waterfall deletion is not expected and should be reported as a bug for our team to investigate.
Sources: New at Clay | Clay.com Enrich People (Waterfalls) [CRM Enrichment] - Clay University Enrich People (Waterfalls) [Automated Inbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Automated Outbound] - Clay University Enrich People (Waterfalls) [Clay 101] - Clay University Enrich People (Waterfalls) [Clay 101] - Clay University Delete content within your workspace | Documentation | Clay University
Jill Y.
·
·
Ok please route this to a person
LuisArturo
·
·
Hey there Jill thanks for reaching out, for the column question here, you were likely running into the Enrichment Column limit here which is 40. As for the Validation columns not being deleted, do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Jill Y.
·
·
Totally! Sorry I did delete them all as I am actively working on this table https://app.clay.com/workspaces/295765/workbooks/wb_0sz3bsp5Q8Deekakhy2/tables/t_0sz3btkYjJWw9NPjbkZ/views/gv_0sz3btkJYGpWf9aPmiK
LuisArturo
·
·
No worries, will just test this out on my end here.
Jill Y.
·
·
Sounds good
LuisArturo
·
·
Was not able to recreate the bug on my end, did you use a particular waterfall when this occurred?
Jill Y.
·
·
It was this one
LuisArturo
·
·
Thank you for clarifying was unable to recreate this either. I will bring this up with the team so we can try to see what happened here. I'll go ahead and close out this ticket now, but don't hesitate to reach out again if you need any help in the future.
Jill Y.
·
·
No worries! Will reopen this ticket if I see it again

Error: Maximum Columns Reached in Table Despite Fewer Columns | Clay