Table Processing Slowdown: Issues with 'Find Contacts at Companies' API | Clay

Table Processing Slowdown: Issues with 'Find Contacts at Companies' API

Hi team, we're seeing quite a slow down in our table processing. We're using "Find Contacts at Companies" + HTTP API call which are very slow. 100/min vs max 5/min currently (they even appear stuck at moments). Is there maybe some ongoing issue??

9 comments

Channeled
APP
·
·
We're not aware of any ongoing issues specifically affecting the "Find Contacts at Companies" feature or HTTP API calls. However, the slowdown you're experiencing could be related to rate limits or API quotas. For the "Find Contacts at Company" action, which uses our Companies, People, and Jobs data sources, there isn't a specified rate limit in the provided information. The slowdown might be due to various factors affecting data processing. To help us investigate further, could you please provide more details about your HTTP API usage? Specifically, can you share any error messages or JSON responses you're receiving from the API calls?
Source: Find Contacts at Company with "Companies, People, and Jobs" | Clay.com
Frane R.
·
·
There are no errors, just very slow processing. Is there a way to see if we are hitting some rate limits?
Channeled
APP
·
·
To check if you're hitting rate limits for the "Find Contacts at Companies" feature and HTTP API calls, you can look at the rate limit settings in your HTTP API integration setup. Here's how: 1. Go to your HTTP API integration configuration. 2. Look for the "Define rate limit" section. 3. Check the "Request Limit" field, which specifies the maximum number of allowed requests. 4. Check the "Duration (in ms)" field, which shows the time window for the request limit. If you're consistently hitting these limits, you might need to adjust your usage or consider increasing the limits if possible. If you need more help, please request human assistance by clicking on "Talk to a person".
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Frane R.
·
·
We are not hitting any limits on the HTTP API, I was wondering if we are hitting some internal Clay limits? (we have a bunch of tables running these requests)
Channeled
APP
·
·
We don't have specific information about internal Clay limits for the "Find Contacts at Companies" feature or HTTP API calls. However, there are a few factors that could affect processing speed: 1. The "Find Contacts at Companies" action uses our Companies, People, and Jobs data sources, which might impact processing time. 2. Running multiple tables with these requests simultaneously could potentially slow down processing. To help diagnose the issue, could you provide more details about: ** The number of tables you're running simultaneously ** The volume of requests you're making * Any specific patterns in the slowdowns If you need further assistance, please request human support by clicking on "Talk to a person".
Sources: Source - Clay Find People with Companies, People, Jobs Find People [Clay 101] - Clay University
Anaum K.
·
·
Hello Frane! Thank you for reaching out! Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Frane R.
·
·
Hey, I think the slowness was due to the issues you had the other day, it seems to have recovered since yesterday.
Bruno R.
·
·
Hi Frane, thanks for following up on this - glad this was resolved. Feel free to reach out if this issue pops up again, I'll close this tread out for now.
Channeled
APP
·
·