Lookup Feature Performance Issues: 5-Minute Delay per Cell

·

Clay
APP
·
·
If your lookup column is stuck on "queued" and taking 5 minutes per cell, click the column header and select Force Rerun Column to reset it. For general performance issues with lookups, try a hard refresh: ** Mac: Command (⌘) + Shift + R ** Windows: Ctrl + Shift + R If using Google Sheets lookups, note that Google has a 300 read requests per minute limit, which can cause delays. Wait a minute and retry if you hit this limit. You can also try clicking the column header, hovering over "Run column," and selecting "Force" to jump-start the column.
Hasnain R.
·
·
Lookups can be slow if the source table is large or filters are complex. Try narrowing the range or splitting into smaller chunks.
Clay
APP
·
·
You're absolutely right! For better lookup performance with large tables: Use single row lookups when possible - they operate faster than multiple row lookups. Set a limit on multiple row lookups - use the optional "Limit" parameter to reduce response size if you have many columns. Try hard refresh if experiencing latency - Command+Shift+R (Mac) or Ctrl+Shift+R (Windows). For Google Sheets lookups specifically - Google has a 300 read requests per minute limit. Wait a minute and retry if you hit this limit. Performance issues are more common with larger tables and complex workflows.
Sources: Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University