Zenrows Performance Issues: Slow Data Retrieval Analysis

Mike R. · 2025-12-02 02:49:44.756885+00

Zenrows running extremely slow today. In past 16 hours it’s only run 7k/50k rows, clay or Zenrows issues?

Zenrows Performance Issues: Slow Data Retrieval Analysis | Clay

Mike R.
·
·
Here's table https://app.clay.com/workspaces/10589/workbooks/wb_b9dgKG59FYMx/tables/t_KzgNWBDjyakf/views/gv_fsJ3ziPynHyY
Clay Support
APP
·
·
That's frustrating—let me help troubleshoot this slowdown.
For Zenrows processing delays, try these steps:
• Break into smaller batches - Large data requests can cause slowdowns
• Hard refresh your browser - Mac: Cmd+Shift+R, Windows: Ctrl+Shift+R
• Check rate limits - Clay implements rate limits for system stability, especially with heavier processes
Performance issues are more likely with larger tables or complex workflows. Since you're processing 50k rows, the system may be pacing the requests to maintain stability.
Try the hard refresh first, then consider splitting your 50k rows into smaller batches of 5-10k to improve processing speed. [1]
Clay Support
APP
·
·
Is that what you were looking for?
Mike R.
·
·
Talk to person
Clay Support
APP
·
·
I understand your frustration, and I’ll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
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!
image.png(93 kB)
Mayato (.
·
·
Hi Mike, thank you for reaching out. Please let me take a look at your table first.
👍1
Mayato (.
·
·
Hi Mike, I’m so sorry for the delayed response. The ZenRows action is processing multiple records in parallel, but because the volume is quite large, it’s taking some time to finish all rows. The speed depends on the maximum concurrency allowed by your ZenRows subscription.
Here is the related ZenRows documentation for reference.
https://docs.zenrows.com/universal-scraper-api/features/concurrency#example-scenario
I hope this clarifies your question but please let us know if you have other questions. Thank you!
Mike R.
·
·
Hi there thanks for the response! It’s definitely not a concurrency issues as I have 350 concurrency with them. Are you guys able to figure out the issue since this hasn't been a problem previously? At this rate it'll take about a week to finish just my zenrows actions
Mike R.
·
·
it's been 26 hours since this started running and concurrency isn't the issue as you can see, I think it's something on Clay's side, can you take a look?
Loading attachments
Natalie H.
·
·
Hey Mike! Thanks for flagging this. Hmmm I can see that all 36,000 rows are running at once for the Zenrows enrichment. Have you been able to run them quickly in a large batch like this before as well?
Mike R.
·
·
Yes I have. As mentioned it wouldn't take a full week to run a single enrichment when I have plenty of concurrency available. It's most certainly a clay batching issue and going extremely slow. If would've known I would've just use zenrows http instead of clays zenrows integration since that is the issue. Can the team look at this since I don’t really have a full week to waste while this single enrichment runs?
Natalie H.
·
·
Thanks for flagging this, and sorry for the trouble! I'm looking at the table now, and did you happen to re-run the column? Watching it live, I'm seeing results come in, so I wanted to confirm whether a re-run kicked off a fresh batch or if this is continuing from the original run. Thanks for your patience on this!
Loading attachments
Natalie H.
·
·
I'll also reach out to our support engineering team to see if it's possible to increase the concurrency in Zenrows so that it meets your 350 limit!
Mike R.
·
·
Hey Natalie - Nope it's all the same queued runs that kicked off 32 hours ago, I haven't rerun anything. And yes if you can figure out why Clay's throttling the requests so hard when there's plenty of concurrency please as this is literally going to take 7 days to complete haha

17 comments