Feedback Needed: Bugs with Clay Lookup Integration and Formula Errors

Hey Team, not sure if you've received this feedback from anyone else yet but Clay has gotten buggy for me in some instances. For example, my lookup integration gives me false results on a specific table sometimes, when I run it again (with the same data) I get the correct result. Similarly, a formula that has been working fine for the past 6 months, suddenly starts giving a wrong result, even the prompt outputs the same formula but the result is wrong. Any insights on this?

7 comments

Channeled
APP
·
·
The issues you're experiencing with your lookup integration and formula in Clay could be due to a few factors: 1. For the lookup integration, inconsistent results might occur if the data in the source table changes between runs. It's also possible that the lookup criteria or matching conditions need adjustment. 2. Regarding the formula suddenly producing incorrect results, this could be related to how the formula is set up. Sometimes formulas assume there will be a response for every row, which isn't always the case. This can lead to errors that cause unexpected outputs. To address these issues, we recommend: 1. Double-check your lookup integration settings and ensure the source data is consistent. 2. Review your formula logic. Consider adding conditional checks, like "if {{response}} exists..." to handle cases where data might be missing. Can you provide more details about the specific lookup integration and formula you're using? This would help us troubleshoot more effectively.
Source: AI Formulas + Conditional Runs [Automated Outbound] - Clay University
Aamir
·
·
And what's the reason for auto-dedupe not working?
Channeled
APP
·
·
Auto-dedupe might not be working because it hasn't been enabled or configured correctly. To use this feature: 1. Open your table settings dropdown. 2. Click the table dropdown menu and select 'Enable/Disable auto-dedupe'. 3. Toggle the auto-dedupe setting on. 4. Select the column to be used for identifying duplicate values. Remember, auto-dedupe only works on a specified column and excludes blank cells and cells with more than 200 characters. If you've followed these steps and it's still not working, you might need to check if you've selected the correct column for deduplication. If issues persist, please request human assistance by clicking on 'Talk to a person'.
Sources: Table management settings | Documentation | Clay University Auto-update and Auto-dedupe Table
Aamir
·
·
I have another issue, my Apollo integration keeps on running for hours even after all the rows have been completed, even if I select fewer rows like 100 or 200 - previously it used to take a few minutes for the enrichment to end, now even if I stop updates manually, it takes hours to end the process
Channeled
APP
·
·
The prolonged running time of your Apollo integration could be due to rate limiting or processing issues. Here are some steps to resolve this: 1. Refresh your browser (Cmd/Ctrl + Shift + R) to ensure you're seeing the most up-to-date status. 2. Check if you've hit Apollo's rate limit. Consider processing data in smaller batches (e.g., 200 rows at a time) to stay within limits. 3. Try running only the affected rows using the error retry option: • Right-click the column • Click "Play" • Select "Run All Rows that haven't run or have errors" 4. If issues persist, you may need to force run the column: • Right-click the column • Hover over "Run Column" > "Force Run All Rows" If these steps don't resolve the issue, request human assistance by clicking on 'Talk to a person' for further troubleshooting.
Sources: Apollo.io integration overview | Documentation | Clay University Run Options
Channeled
APP
·
·
Channeled
APP
·
·
Thank you so much for sharing your feedback Aamir!