Troubleshooting Duplicate Record Issues in Clay to Cargo API Transfer

Ksenia B. · 2025-06-25 07:29:21.285164+00

I'm sending data from Clay table to Cargo via HTTP API. I have an issue that the same record is being sent twice. What can be wrong? My Clay table -

Troubleshooting Duplicate Record Issues in Clay to Cargo API Transfer | Clay

5 comments

· Sorted by Oldest

Clay
APP
·
·
This could be happening due to auto-update settings in your HTTP API integration. By default, columns update whenever you add a new row, which might trigger duplicate sends. To fix this: 1. Check your HTTP API column's auto-update setting 2. Toggle it off if you don't want automatic updates 3. Consider using conditional run criteria to control when the API call executes Could you share your JSON body configuration so I can help troubleshoot further?
Sources: HTTP API integration overview | Documentation | Clay University HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Bo (.
·
·
Hey, I saw that you enabled Auto Dedupe—did that help? In most cases, duplicates in the table can cause the same record to be sent twice. Another possible reason is if any of the column dependencies were updated, which can trigger a rerun and resend the data. Let me know if you’re still seeing duplicates or need help checking dependencies.
Ksenia B.
·
·
I still experience the same issue. I even have enabled the deduplication feature but it still sends the same HTTP API request twice. Working with a new table and still experiencing the same issue - https://app.clay.com/workspaces/261968/workbooks/wb_0szqs5hGwRDaFotGWiV/tables/t_0szsso3AGswAvPZVT6V/views/gv_0szsso3bEMbxTNWDaUx
Smit V.
·
·
Hi Ksenia, thank you for reaching out! 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
Smit V.
·
·
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?

Clay
APP
·
·
This could be happening due to auto-update settings in your HTTP API integration. By default, columns update whenever you add a new row, which might trigger duplicate sends. To fix this: 1. Check your HTTP API column's auto-update setting 2. Toggle it off if you don't want automatic updates 3. Consider using conditional run criteria to control when the API call executes Could you share your JSON body configuration so I can help troubleshoot further?
Sources: HTTP API integration overview | Documentation | Clay University HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Bo (.
·
·
Hey, I saw that you enabled Auto Dedupe—did that help? In most cases, duplicates in the table can cause the same record to be sent twice. Another possible reason is if any of the column dependencies were updated, which can trigger a rerun and resend the data. Let me know if you’re still seeing duplicates or need help checking dependencies.
Ksenia B.
·
·
I still experience the same issue. I even have enabled the deduplication feature but it still sends the same HTTP API request twice. Working with a new table and still experiencing the same issue - https://app.clay.com/workspaces/261968/workbooks/wb_0szqs5hGwRDaFotGWiV/tables/t_0szsso3AGswAvPZVT6V/views/gv_0szsso3bEMbxTNWDaUx
Smit V.
·
·
Hi Ksenia, thank you for reaching out! 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
Smit V.
·
·
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?