Hey Clay S. - Not sure if this has previously been reported but I am finding the "Auto-dedupe" in the table settings requires 2 attempts before the table automatically dedupes based on the selected row. What typically happens is I configure the auto de-dupe and click "save changes". Then the side panel closes but nothing happens in the table (this is both true on smaller and larger tables). I then need to reopen the "auto-dedupe" setting, (sometimes I need to reconfigure the column to dedupe on - sometimes it remembers the column I selected on first try). Then when I click "save changes" for a second time, the deduping starts to work automatically as intended. See loom vid here Link to Clay table here
The auto-dedupe feature should work immediately after configuration. To set it up correctly: select the Auto-dedupe icon at the bottom right of your table, toggle on "Enable automatic deduplication," choose your dedupe column, and click "Save Changes." [1]
Auto-dedupe continuously monitors the specified column to detect duplicates by retaining the oldest row and deleting duplicates, excluding blank cells and cells with over 200 characters. [2]
The behavior you're experiencing where it requires two attempts isn't the expected functionality. This appears to be a technical issue that may need further investigation.
Are you experiencing this issue consistently across multiple tables, or is it specific to certain table types or sizes?
If you still need help resolving the auto-dedupe issue, I’m here to assist. Would you like to provide more details about the tables or steps you’re using so we can continue troubleshooting?
If you still need help resolving the auto-dedupe issue, I’m here to assist. Would you like to provide more details about the tables or steps you’re using so we can continue troubleshooting?
This happens to me every time as well.
Thanks for confirming this issue affects you as well. Since multiple users are experiencing the same auto-dedupe bug where it requires two attempts to save and activate, this appears to be a consistent technical issue that needs investigation.
To help us research and resolve this, it would be helpful if you could also provide a link to one of your tables where you've experienced this issue, along with any specific error messages you might have seen.
If you need further help with this bug, please request human assistance by clicking on "Talk to a person."
Did that answer your question?
I’m sorry for the ongoing trouble with the auto-dedupe feature and hope my previous messages were helpful. Would you like to share more details about your experience or any other issues you’re encountering so I can assist further?
