Clay Instance Backlog Due to HTTP Request Overload

My entire clay instance is backlogged from our https requests. this 6k table has been processing for 24 hours. Probably because we are processing another 40 tables right now that each have 9+ http nodes

👀1

2 comments

Channeled
APP
·
This processing delay could be due to several factors. Here's how to address it:1. Break down your data requests into smaller batches instead of processing all 6k records at once. 2. Check your workspace's rate limits: • Processing is limited to 10 records per second • Maximum burst capacity is 20 records • When multiple HTTP requests are running simultaneously (as in your case with 40 tables), you'll need to adjust your approach to stay within these limitsTo improve processing speed:** Make your search queries more specific and well-defined ** Monitor your usage limits and API quotas * Verify your network connection stability Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.