.png){kind=logo}
Troubleshooting Slow Table Lookups in Database Queries
why are my tables running so slow when doing a lookup in another table? it has been an hour and nothing has progressed:
why are my tables running so slow when doing a lookup in another table? it has been an hour and nothing has progressed:
Performance issues with table lookups typically occur when there are large tables and multiple actions running simultaneously. If your lookup is stuck on "queued," click the column header and select Force Rerun Column to reset it. For general performance issues, try a hard refresh: ** Mac: Command + Shift + R ** Windows: Ctrl + Shift + R You can also click the column header, hover over "Run column," and select Force to jumpstart the column run. For better performance, use "Lookup Single Row in Other Table" instead of multiple row lookups when you only need one result, as it operates faster.
Most users facing this or similar kind of issue Jack.
Hey - Jack Linked Table Is Too Large or Has Complex Formulas Break large tables into smaller linked views Avoid nested lookups or chained formulas during enrichments Missing Unique Identifiers in Lookup Make sure you're matching on a clean, unique column (like email or domain) Try “Manual Run” Instead of Auto-Run Turn off auto-run Use “Run Row” to test 1–2 rows at a time Clay Backend Delay (Temporary) If it's hanging for an hour, Clay servers may be backed up Check Clay Status Page or ask in Slack
For stuck lookups: ** Click the column header and select "Force Rerun Column" to reset queued lookups ** Try a hard refresh: Mac (Command + Shift + R), Windows (Ctrl + Shift + R) Performance optimization: ** Use "Lookup Single Row in Other Table" instead of multiple row lookups when you only need one result - it operates faster ** Break large tables into smaller linked views ** Use the Limit option in multiple row lookups to reduce response size ** Ensure you're matching on clean, unique identifiers like email or domain For backend delays: ** Performance issues are more likely with larger tables or complex workflows ** If lookups hang for extended periods, try the Force option under "Run column" in the column header dropdown
Hi Jack, thanks for reaching out and apologies for the frustration here. The issue here might have been due to latency issues affecting some Clay tables, which have now been resolved. Everything should be loading as expected again. Thanks so much for your patience while we worked through it. If you're still experiencing any issues, please let us know.