Troubleshooting Slow Lookup Performance for Large Tables | Clay

Troubleshooting Slow Lookup Performance for Large Tables

looking up rows in another table is running extremely slow. Maybe this is normal, as I have not run so many look-ups in a table, but for a list of 6,800 rows, i am running look-ups to another table but they are still running after 8 hours. Is this normal?

15 comments

Clay
APP
·
·
8 hours for 6,800 lookup rows is not normal performance. Performance issues can occur with larger tables and complex workflows like linked tables. For better performance, consider using "Lookup Single Row in Other Table" instead of multiple row lookups, as single row lookups operate faster. Try a hard refresh to resolve potential latency issues: - Mac: Command (⌘) + Shift + R (Chrome/Firefox) or Option (⌥) + Command (⌘) + E (Safari) - Windows: Ctrl + F5 or Ctrl + Shift + R
Sources: Lookup Rows | Documentation | Clay University Lookup Rows | Documentation | Clay University
Matthew H.
·
·
https://app.clay.com/workspaces/395159/workbooks/wb_0szsnr7BGeyZwKgdYix/tables/t_0szsrmjEWvTEnrovTgo/views/gv_0szsrmjn3ZcD479UxjN
Clay
APP
·
·
Hi Matthew! Thanks for reaching out, and sorry to hear that you are experiencing this. Happy to take a look for you.
Hunain F.
·
·
Matthew H. I can do this for you just DM me
Hunain F.
·
·
Send me your table in my DM
Clay
APP
·
·
Hey Matthew! I took a look at your table, and it looks like your account has run out of credits this month. As a result, the lookup column was probably stuck and didn't continue running. You can purchase credits under settings --> Plan & billing, like shown below. Please let me know if you have any other questions, or if there's anything else I can help with. Happy to help, thanks!
(243 kB)
Matthew H.
·
·
do I need credits to lookup rows in another table?
Matthew H.
·
·
it has already ran several thousand rows without me having any credits
Clay
APP
·
·
Hi Matthew, this is a great point! Thank you for flagging this, and you are totally right.
Clay
APP
·
·
Hey Matthew! Do you mind refreshing the page and trying to re-run the column? Sometimes when we experience an outage on our end, it won't refresh the table and can cause actions to get stuck. This may be what happened here.
Clay
APP
·
·
Please keep me posted if it works out, and happy to answer any followup questions! Thanks!
Matthew H.
·
Thanks I have tried this several time throughout the day. The records are updating but very slowly. Sometimes 1-2 rows per hour
Clay
APP
·
·
Hi Matthew - totally hear you. The engineering team is aware that “Lookup in Single Row” steps can sometimes take longer to run, and they’re actively working on improving performance there. I’ve passed along your feedback to help prioritize this.
Matthew H.
·
·
Thanks a lot
Clay
APP
·
·
Hi Matthew! Thank you so much for your patience here! I wanted to update you on our timeline for getting this issue fixed; our engineering team is experiencing some backend issues, but they hope to get it working by today. I'll keep you updated as soon we learn more. Thanks!