Urgent: Repeated Duplicate Destination Error in Mappings

Ben H. · 2025-01-29 15:36:03.25966+00

Hi I keep getting mappings that say they ahve a duplicate destination (they don’t this is a bug). I’ve fixed this around 5 times now, and it keeps happening again. Please can you look into this, pretty urgently (for a client release). Thank you!

Urgent: Repeated Duplicate Destination Error in Mappings | Clay

Channeled
APP
·
·
This issue might be related to invalid or conflicting data configurations in your mappings. Here's how you can resolve it: 1. First, check your API key configuration: • Go to Settings > Connections • Search for Clay and verify your API key is properly connected 2. If you're still experiencing issues, the error may be due to: • Writing to deleted columns • Sending data to tables that reference another tableTo fix this: 1. Reconfigure your Write to Table integrations 2. Verify all columns and tables exist and are properly set up 3. Remove and re-add the integrations to clear any misconfigurationsIf these steps don't resolve your issue, please explicitly ask for a human agent in this conversation for further assistance, as this may require direct investigation of your specific setup. Source: Write to table integration overview | Documentation | Clay University
Tanvi R.
·
·
Hi Ben, thanks for reaching out! Happy to take a look here for you
Tanvi R.
·
·
Hey Ben, I just deleted the input and re-added it to write to table and it saved correctly. Please try running this now and let us know if you have any further questions!
Ben H.
·
·
I’ve done this a tonne of times
Ben H.
·
·
The error keeps coming back
Ben H.
·
·
This is for a client project and I’m trying to get it signed off, but don’t feel confident with it in this state
Tanvi R.
·
·
t looks like this might just be a user interface bug, when I check the table it is writing to I see both of these columns are filled and have values. Let me know if there are any incorrect results you're seeing
Ben H.
·
·
Ok cool so I should be able to run the table regardless? It’s just the domain’s important for the flow so i don’t want it to mess anything up
Tanvi R.
·
·
Yes you should be able to run the table correctly
Channeled
APP
·
·
Hi Ben H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Ben H.
·
·
Ok this definitely did not run the table correctly and has caused significant disruption to my clients project & cost a lot of resource/credits (external to Clay).
Ben H.
·
·
https://app.clay.com/workspaces/339655/tables/t_HTyvPq4TobGm/views/gv_vWDA8ME8seeo All of the fields were correctly mapped, and now the bug is back, the domain has been unmapped for some reason now too (1-24 & Prospect - Go Sell Wireless) I haven’t checked the others, but I’ve just received a complaint from the client about this
Ben H.
·
·
Please can you look into this ASAP.
Ben H.
·
·
Hey Tanvi R. / team, any updates on this please?

31 comments