Clay Performance Issues: Slow Lead Status Lookup for Smartlead
Anyone having issues with Clay today? Running a lead status lookup for Smartlead and so far it's taken 20 minutes and only searched 500
Anyone having issues with Clay today? Running a lead status lookup for Smartlead and so far it's taken 20 minutes and only searched 500
The Lookup Lead Status in Campaign with Smartlead.ai integration queries lead status within campaigns by providing a campaign ID and email address to determine if leads have completed, replied, exist, or are progressing through campaigns. Performance issues with the lookup can occur due to several factors including duplicate lead settings, blocked leads in your account, or reaching your account's lead limit. What's the size of your campaign and are you running the lookup on all leads simultaneously or in smaller batches?
It is only 2100 leads and I am running it in one search
Running 2100 leads in one batch can cause performance issues. The slow processing is likely due to API rate limits or system constraints when handling large datasets simultaneously. For better performance, try processing your leads in smaller batches of around 50-100 rows at a time instead of running all 2100 at once.This approach helps avoid hitting rate limits and reduces the likelihood of timeouts or errors. If the lookup appears stuck, you can click the column header and select "Force Rerun Column" to reset it.
Hi Jonathan, thanks for reaching out to support!
Let me take a quick look at your table here to see what is going on
Ok Jonathan, I understand you're experiencing slow performance with your bulk update of 2100 leads. This is a common issue when processing large datasets, and I have some recommendations to help improve the situation. I'd suggest stopping the current update process immediately by clicking "Stop Runs" on the column that's currently processing. Large bulk updates can sometimes get stuck in queue states or experience significant slowdowns due to rate limits from external APIs or system processing constraints. Once you've stopped the current run, wait a minute or two to allow any background processes to clear. After stopping, try running the updates in smaller batches rather than all 2100 rows at once. You can do this by filtering your table to show only a subset of rows (perhaps 200-500 at a time), then running the column on just those filtered rows. This approach helps avoid rate limiting issues and generally processes much faster than large bulk operations. You can repeat this process in batches until all your leads are updated. This method is particularly effective for avoiding the queuing bottlenecks that often occur with large datasets and will give you better visibility into the progress of your updates.
Is this always going to be an issue Luca P.? I've run this before and it's been super quick, unusual it's so slow this time
And this is a relatively small list, if I have to keep batching it up, then it'll become pretty slow and manual
This shouldn't always be an issue, I'll take a deeper look into this problem and see if there is something going on. However, in the meantime if the issue is still happening, the last thing I would try is to just do a Hard Refresh Mac: ** Chrome and/or Firefox = Press Cmd + Shift + R ** Safari = Press Cmd + Option + R PC: * Chrome, Firefox, Microsoft Edge = Press Ctrl + F5
Yeah I tried a hard refresh, logged out of Clay and back in, fresh browser - nothing changed it. Still super slow
Hey there Jonathan thanks for reaching out, this was occurring do to an issue were dealing that has been recently resolved, just to confirm if you are seeing this in other tables as well?
LuisArturo I was only running this one table so unaware of how other tables were running
Hey Jonathan! Within this table does the issue still persist? Happy to take a deeper look if so. As my colleague mentioned, we had an issue recently that has since been resolved that affected the initial action.
Seems to be working now more quickly Hari K.
Awesome!