Join the Community

Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps

Community Guidelines

Powered by Tightknit

Issue with Clay Table: Data Not Populating After Import

·

·

Hi Clay Support, I’m experiencing a persistent issue when trying to find and populate people into a Clay table. Here’s what’s happening:

I opened the data source and can see that 535 rows were added at a certain time.
However, after the import, none of those people are populating into the table.
I’ve followed all suggested troubleshooting steps, including:

Logging out and logging back in
Doing a hard refresh with Command + Shift + R
Clearing my browser cache
Ensuring that all filters are off
Creating new tables in different workbooks and attempting the import again

Despite all of this:

The table still says “loading delays for larger tables”, but this is only 500 people, so not that large.
When I attempt to re-run the source, I get the message “0 rows added”, presumably due to deduplication being turned on.
However, those rows never actually appeared, so I’m confused why they’re being counted as duplicates.

This issue is blocking me from progressing with my workflow, and I can’t figure out what’s going wrong. Could someone please take a look or let me know what else I can try? Thanks so much, Muttley

13 comments

Clay
APP
·
·
This issue occurs when records are deleted from a people search - you cannot re-import them to the same table again. To resolve this, you'll need to reconfigure the same people search from scratch in a new table. The "0 rows added" message appears because our system remembers the deleted records as duplicates, even though they're no longer visible in your table. Additionally, check if auto-dedupe is enabled - click the Auto-dedupe icon at the bottom right of your table and toggle off "Enable automatic deduplication" if it's on. If you need further help, request human assistance by clicking on "Talk to a person."
Sources: Auto-update and Auto-dedupe Table Table management settings | Documentation | Clay University Sources | Documentation | Clay University
Grant R.
·
·
It seems no-one is able to populate tables currently from any input. I sent 500 webhooks successfully but the tables are not populating the results
1
1
Muttley M.
·
·
Grant R. yeah just scrolled up
1
Muttley M.
·
·
oops
Clay
APP
·
·
This sounds like a performance issue affecting table loading. Try a hard refresh first: ** Mac: Command + Shift + R ** Windows: Ctrl + Shift + R If webhooks sent successfully but aren't populating, the issue may be loading delays with larger tables. For stuck columns, click the column header and select Force Rerun Column to reset it.You can also hover over "Run column" and select Force to jumpstart the column. Performance issues are more common with larger tables or complex workflows.Note that webhooks have rate limits of 10 records per second with 20 record burst capacity.
Source: Import Data to Clay Using Webhooks
Grant R.
·
·
These AI responses are quite annoying when theres no human to actually help 🙂
Clay
APP
·
·
This appears to be a performance issue with loading delays affecting larger tables.Empty spaces in rows are usually due to loading delays—larger tables can take longer to update. For stuck columns showing data that won't populate: ** Click the column header and select Force Rerun Column to reset it ** Hover over "Run column" and select Force to jumpstart the column Note that webhooks have rate limits of 10 records per second with 20 record burst capacity, which could cause delays with bulk imports. If the issue persists after forcing column reruns, request human assistance by clicking on "Talk to a person."
Source: Import Data to Clay Using Webhooks
Jakob G.
·
·
I'm having the exact same issue and haven't been able to get any helpful support for almost a week now
Muttley M.
·
·
Jakob G. a week!
Muttley M.
·
·
Mine has been two days
Nicole G.
·
·
Hi Muttley, Thanks for reaching out to support. I wanted to check in and see if you are still experiencing this issue. We were experiencing a bug earlier creating a latency issue, it should now be resolved. Could you let me know if the issue persists? If anything still seems off, feel free to let me know, happy to help!
Muttley M.
·
·
all good
Nicole G.
·
·
Glad to hear it's resolved, please feel free to reach out with any additional questions you may have