Troubleshooting Daily Clay Table Sync Issues with Salesforce Records

Lana M. · 2025-12-17T19:11:39.834Z

I have a Clay table pull from a Salesforce report, and it is scheduled to refresh daily. Currently I have 13 records in Clay, but there are 16 records in Salesforce. I've tried to manually "run now" but the new records are not appearing in Clay. What am I missing?

Troubleshooting Daily Clay Table Sync Issues with Salesforce Records | Clay

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
The most likely issue is with your Uniqueness Fields setting. Since Salesforce reports don't have unique identifiers, Clay uses these fields to identify each row and prevent duplicates. [1]
If you didn't select any uniqueness fields, Clay uses the entire row as the unique identifier, which can cause sync issues when data changes. [2]
Also check that your report is in tabular format without groupings - reports with groupings won't import properly.
To fix this, go back to your source settings and specify which fields should be used as unique identifiers for each record. This will help Clay properly sync the new records from Salesforce.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the discrepancy between your Salesforce report and Clay table, I’m here to assist. Would you like to provide more details about your current setup or any other issues you’re encountering?
Lana M.
·
·
No - I am using the SFDC ID as the uniqueness field and yes the report is in a tabular format
Clay Support
APP
·
·
Thanks for the details. I’m routing you to our human team now so they can assist you further with this issue.
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)
Lana M.
·
·
https://app.clay.com/workspaces/312973/workbooks/wb_0t74lqppB43ZWXpdJP3/tables/t_0t7a0uxtzQqFthKpkEP/views/gv_0t7a0uygEFY67Fv7QQR
LuisArturo
·
·
Hey there Lana thanks for reaching out, taking a look here for you.
1
LuisArturo
·
·
Quick question here Lana, are these records public, as in are there any sharing settings that these missing reports have
Lana M.
·
·
I have full admin access to both Clay & Salesforce - so there should be no sharing restrictions
LuisArturo
·
·
Ok thank you for confirming just wanted to make sure this was not the case. Let me check in with the team here and see what might be going on here.
LuisArturo
·
·
Hey there Lana taking a look here, what is happening here is that the 3 missing reports are duplicates of existing records in your Salesforce and you happen to have the auto dedupe enabled preventing them from being added here. For clarification these duplicates are two additional records for Craig Whitmer and one duplicate for Vikas Bhambri.
Lana M.
·
·
Ahhh, okay that makes sense - so it is working as expected then. Thank you for looking into this Luis! Appreciate it
LuisArturo
·
·
No worries happy to help ehre

Clay Support
APP
·
·
The most likely issue is with your Uniqueness Fields setting. Since Salesforce reports don't have unique identifiers, Clay uses these fields to identify each row and prevent duplicates. [1]
If you didn't select any uniqueness fields, Clay uses the entire row as the unique identifier, which can cause sync issues when data changes. [2]
Also check that your report is in tabular format without groupings - reports with groupings won't import properly.
To fix this, go back to your source settings and specify which fields should be used as unique identifiers for each record. This will help Clay properly sync the new records from Salesforce.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the discrepancy between your Salesforce report and Clay table, I’m here to assist. Would you like to provide more details about your current setup or any other issues you’re encountering?
Lana M.
·
·
No - I am using the SFDC ID as the uniqueness field and yes the report is in a tabular format
Clay Support
APP
·
·
Thanks for the details. I’m routing you to our human team now so they can assist you further with this issue.
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)
Lana M.
·
·
https://app.clay.com/workspaces/312973/workbooks/wb_0t74lqppB43ZWXpdJP3/tables/t_0t7a0uxtzQqFthKpkEP/views/gv_0t7a0uygEFY67Fv7QQR
LuisArturo
·
·
Hey there Lana thanks for reaching out, taking a look here for you.
1
LuisArturo
·
·
Quick question here Lana, are these records public, as in are there any sharing settings that these missing reports have
Lana M.
·
·
I have full admin access to both Clay & Salesforce - so there should be no sharing restrictions
LuisArturo
·
·
Ok thank you for confirming just wanted to make sure this was not the case. Let me check in with the team here and see what might be going on here.
LuisArturo
·
·
Hey there Lana taking a look here, what is happening here is that the 3 missing reports are duplicates of existing records in your Salesforce and you happen to have the auto dedupe enabled preventing them from being added here. For clarification these duplicates are two additional records for Craig Whitmer and one duplicate for Vikas Bhambri.
Lana M.
·
·
Ahhh, okay that makes sense - so it is working as expected then. Thank you for looking into this Luis! Appreciate it
LuisArturo
·
·
No worries happy to help ehre