Discrepancy in Attendance Rows: Only 7 Showed Up Instead of 29

Brendan S. · 2025-11-12 16:46:55.844412+00

this is showing 29 rows Sent (screenshot below) but when i got to the table, there only 7 people who have showed up (screenshot below) it has been 15 minutes. i tried running that row again (manually) and still only 7 show up.

Clay Support
APP
·
·
This discrepancy between 29 rows sent and only 7 showing could be due to display issues or row limits. First, check if a row limit is applied by clicking the Rows button at the top of your table to see if there's a limit set. [1]
If you're experiencing display issues with filtered data, try clearing your cache and refreshing your screen, as this can resolve front-end performance issues.
If your write to table function isn't processing correctly, try using the Force Run option in the table settings, or delete the affected column and create a fresh one, then re-map your data.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with the row count discrepancy, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Brendan S.
·
·
no, that did not solve it
Clay Support
APP
·
·
I'm sorry to hear that didn't help. I'll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Brendan S.
·
·
this table - https://app.clay.com/workspaces/584068/workbooks/wb_0t0h3qgaNvHjJ6XH7Np/tables/t_0t1aweyCzef6MYDRYZT/views/gv_0t1aweysFuVQbUTA6Ti and this table - https://app.clay.com/workspaces/584068/workbooks/wb_0t0h3qgaNvHjJ6XH7Np/tables/t_0t1azingFCBbGMMBM9d/views/gv_0t1azioeWwFV3uCzwTD
Smit V.
·
·
Hey Brendan, took a quick look and I believe the reason you are seeing only a subset of people is because you have Auto-dedupe enabled on the "Person's LI URL" column in the destination table and that will automatically remove people if the same people reacted to different posts.
Brendan S.
·
·
ah interesting. how can i confirm this to be true?
Brendan S.
·
·
is there a way to do a time frame? eg: 'has not engaged with a post in the last {90 days}'
Smit V.
·
·
You could look at the Table History and see the LinkedIn Profiles that got automatically deleted
Loading attachments
Brendan S.
·
·
amazing. very helpful, thank you.
Brendan S.
·
·
is it possible to build this inside a Clay table? eg: pass ALL records, but then do some sort of check to say "if dupe found, then look up date" and "if in last 90 days, then don't Run". does this make sense?
Brendan S.
·
·
basically - i don't want to ignore someone who may have liked a post 8 months ago.
Smit V.
·
·
There's no easy way to do that, but here's an approach that might work. You could use a combination of the lookup row function to find the duplicate, then add a function column to determine how old it is. From there, you can use those values as run conditions in your upstream enrichments.

19 comments