Issues with SalesForce Lookup Record Not Finding Matches

Patryk W. · 2025-11-24 11:44:48.696033+00

I was using SalesForce Lookup Record action 3 days ago and it could find matching in our database. Today I made a duplicate of this column and rerun this column and it cant find any matches. Why?

Issues with SalesForce Lookup Record Not Finding Matches | Clay

11 comments

· Sorted by Oldest

Clay Support
APP
·
·
The Salesforce Lookup Record action may fail to find matches in a duplicated column due to changes in search criteria or sync timing. Ensure the following:
Exact Match setting is consistent—by default, it uses "contains" unless toggled to exact.
Search Operator (AND/OR) and filter fields are correctly configured in the duplicate.
Data in Salesforce hasn't changed or been restricted by permissions.
Also, manually refresh the column to ensure latest data is synced . If issues persist, try Force Rerun Column . [1] [2]
Clay Support
APP
·
·
Did that answer your question?
Patryk W.
·
·
it is the same column and it worked 3 days ago but today it can't find any matches
Clay Support
APP
·
·
Since the same column worked 3 days ago but isn't finding matches now, try these steps:
Force Rerun Column: Click the column header and select "Force Rerun Column" to reset any stuck processes.
Manual Refresh: Use the "Run now" button to immediately sync the latest data from Salesforce.
Check Salesforce Data: Verify that the records still exist in Salesforce and haven't been modified or restricted by permissions.
The issue is likely related to data sync timing or the column getting stuck rather than configuration changes. [1]
Clay Support
APP
·
·
Did that answer your question?
Patryk W.
·
·
record still exist
Clay Support
APP
·
·
Since the record exists and the column worked previously, this is likely a stuck column issue. Try Force Rerun Column by clicking the column header and selecting this option to reset any stuck processes.
You can also trigger a manual refresh using the "Run now" button to immediately sync the latest data from Salesforce.
If you're still having issues after trying these steps, I'd recommend using Sculptor (our built-in AI tool in the top-right corner) to help troubleshoot your Salesforce workflow setup. Let me know if Sculptor helps or if you need further assistance! [1]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with your Salesforce Lookup Record action, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Patryk W.
·
·
close the ticket please
Clay Support
APP
·
·
I'm here to help with anything else you might need. Feel free to reach out whenever you have more questions or issues.

Clay Support
APP
·
·
The Salesforce Lookup Record action may fail to find matches in a duplicated column due to changes in search criteria or sync timing. Ensure the following:
Exact Match setting is consistent—by default, it uses "contains" unless toggled to exact.
Search Operator (AND/OR) and filter fields are correctly configured in the duplicate.
Data in Salesforce hasn't changed or been restricted by permissions.
Also, manually refresh the column to ensure latest data is synced . If issues persist, try Force Rerun Column . [1] [2]
Clay Support
APP
·
·
Did that answer your question?
Patryk W.
·
·
it is the same column and it worked 3 days ago but today it can't find any matches
Clay Support
APP
·
·
Since the same column worked 3 days ago but isn't finding matches now, try these steps:
Force Rerun Column: Click the column header and select "Force Rerun Column" to reset any stuck processes.
Manual Refresh: Use the "Run now" button to immediately sync the latest data from Salesforce.
Check Salesforce Data: Verify that the records still exist in Salesforce and haven't been modified or restricted by permissions.
The issue is likely related to data sync timing or the column getting stuck rather than configuration changes. [1]
Clay Support
APP
·
·
Did that answer your question?
Patryk W.
·
·
record still exist
Clay Support
APP
·
·
Since the record exists and the column worked previously, this is likely a stuck column issue. Try Force Rerun Column by clicking the column header and selecting this option to reset any stuck processes.
You can also trigger a manual refresh using the "Run now" button to immediately sync the latest data from Salesforce.
If you're still having issues after trying these steps, I'd recommend using Sculptor (our built-in AI tool in the top-right corner) to help troubleshoot your Salesforce workflow setup. Let me know if Sculptor helps or if you need further assistance! [1]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the issue with your Salesforce Lookup Record action, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other challenges you’re facing?
Patryk W.
·
·
close the ticket please
Clay Support
APP
·
·
I'm here to help with anything else you might need. Feel free to reach out whenever you have more questions or issues.