Smartlead Lookup Lead Feature Taking Hours to Retrieve Data

Sergio P. · 2025-10-31 01:59:46.400176+00

I’m using the lookup lead in campaign feature for Smartlead, but it’s taking hours to retrieve any data

Smartlead Lookup Lead Feature Taking Hours to Retrieve Data | Clay

11 comments

· Sorted by Oldest

Clay Support
APP
·
·
When your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it and get things moving.
You can also try a hard refresh:
Windows: Ctrl + Shift + R
Mac: Cmd + Shift + R
If the column is still stuck, click the column header, hover over Run column, and select Force to jump start the run.
Clay Support
APP
·
·
Is that what you were looking for?
Sergio P.
·
·
human
Clay Support
APP
·
·
I see you're waiting a long time for data retrieval. Would you like me to connect you with a human agent? Or if you provide more details, I can continue to assist you.
Sergio P.
·
·
human
Clay Support
APP
·
·
I’m routing you to our human team now. They’ll be able to assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Sergio P.
·
·
https://app.clay.com/workspaces/433367/workbooks/wb_0t4snd5kv93JkrtYuNr/tables/t_0t4t8pmrrJ5VYGnVvdh/views/gv_0t4t8pmzjUyFYHnJasS
Hunain F.
·
·
Hey Sergio P., That usually happens when your Smartlead campaign has a large number of leads or when Smartlead’s API is throttling requests. You can fix this by reducing the lookup load Go to your Clay table and add a filter to check only the specific campaigns or smaller batches of leads instead of running the lookup for all at once then re run the enrichment it’ll process much faster
Mitch H.
·
·
Hey Sergio, checking in here. Looks like this has since been resolved, but I want to mention that this can indeed happen when you are processing many requests at once. For larger tables, I recommend running these calls in batches of a few hundred rows at a time. Hope this helps :)
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
When your lookup column is stuck on "queued," click the column header and select Force Rerun Column to reset it and get things moving.
You can also try a hard refresh:
Windows: Ctrl + Shift + R
Mac: Cmd + Shift + R
If the column is still stuck, click the column header, hover over Run column, and select Force to jump start the run.
Clay Support
APP
·
·
Is that what you were looking for?
Sergio P.
·
·
human
Clay Support
APP
·
·
I see you're waiting a long time for data retrieval. Would you like me to connect you with a human agent? Or if you provide more details, I can continue to assist you.
Sergio P.
·
·
human
Clay Support
APP
·
·
I’m routing you to our human team now. They’ll be able to assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Sergio P.
·
·
https://app.clay.com/workspaces/433367/workbooks/wb_0t4snd5kv93JkrtYuNr/tables/t_0t4t8pmrrJ5VYGnVvdh/views/gv_0t4t8pmzjUyFYHnJasS
Hunain F.
·
·
Hey Sergio P., That usually happens when your Smartlead campaign has a large number of leads or when Smartlead’s API is throttling requests. You can fix this by reducing the lookup load Go to your Clay table and add a filter to check only the specific campaigns or smaller batches of leads instead of running the lookup for all at once then re run the enrichment it’ll process much faster
Mitch H.
·
·
Hey Sergio, checking in here. Looks like this has since been resolved, but I want to mention that this can indeed happen when you are processing many requests at once. For larger tables, I recommend running these calls in batches of a few hundred rows at a time. Hope this helps :)
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!