Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Learn Clay here
Clay Cup

Powered by Tightknit

Troubleshooting Auto-Dedupe Issues in Clay: Key Steps and Tips

·Oct 17, 2025 05:08 PM·

I have already posted a bug in clay and no one is doing anything about this so I will post again Auto-dedupe continuously monitors a specified column but only detects duplicates when new rows are added or existing rows are edited. Since you're using lookups and write to table operations, the auto-dedupe may not trigger if the data isn't being written as "new rows" to Table D. Try these steps:

1.
Ensure auto-update is enabled for Table D - this runs all columns when rows are added/edited
2.
Check that your write to table integration is configured to add new rows rather than just updating existing cells
3.
Verify the auto-dedupe column selection is correct - it should be the company domain or unique identifier

Auto-dedupe excludes blank cells and cells over 200 characters, so ensure your dedupe column meets these criteria. I've also included a screenshot and the workbook https://app.clay.com/workspaces/781608/workbooks/wb_0t3s04bopa5eF7pGoaj

Loading attachments

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
Based on your screenshot, auto-dedupe is correctly enabled on the "Company Domain" column. However, auto-dedupe only triggers when new rows are added or existing rows are edited. [1]
Since you're using lookups and write to table operations, try these solutions:
1. Enable auto-update on Table D
Click the table name → Select "Enable auto-update"
This ensures all columns run when rows are added/edited [2]
2. Force run the write to table column
If the write to table function isn't processing correctly, use Force Run in table settings
Or delete the column, create a fresh one, and re-map your data
3. Verify your write to table configuration
Ensure it's set to add new rows (not just update existing cells) [3]
If the issue persists after trying these steps, click "Talk to a person" for human assistance with your specific workbook.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the auto-dedupe issue, I’m here to assist further. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Vishal S.
·
·
More evidence
Loading attachments
Clay Support
APP
·
·
Your screenshot shows auto-dedupe is working correctly — 174 duplicate records have been automatically deleted, including multiple iproov.com entries. [1]
Auto-dedupe monitors your specified column and removes duplicates when new rows are added or existing rows are edited. The deduplication history confirms this is functioning as designed.
If you're experiencing a different issue with your write to table workflow, ensure:
Auto-update is enabled on Table D so columns run when rows are added/edited [2]
Your write to table is configured to add new rows rather than update existing cells
What specific behavior are you expecting that isn't happening?
Clay Support
APP
·
·
I understand this has been frustrating, and I’m here if you need more help with the auto-dedupe or write to table setup. Would you like to share more about what you’re trying to resolve or any other details?
Vishal S.
·
·
Everything is configured correctly. Please put me through to a support assistant
Clay Support
APP
·
·
I understand your frustration, and I’m connecting you to a human support assistant now who can help further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
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!
Loading attachments
Mitch H.
·
·
Hey Vishal, happy to help! Could you let me know a bit about what is going wrong. From what I see this functionality seems to be working as intended.
Vishal S.
·
·
Well no I have rows being added to a final table in my workflow and they need to be automatically deduped but they are not
Vishal S.
·
·
Look at the screenshot they show evidence of this
Bo (.
·
·
Vishal - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Mitch H.
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog.
For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change.
So what happens now?
Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you.
Do you have any further questions before I step away from this conversation until I have an update for you?