Error with Claygent Column Despite Multiple Force Runs

prateek · 2025-10-28T15:12:20.416Z

Getting ERROR specifically on this claygent column , even after FORCE RUNNING multiple times @Clay S.

Error with Claygent Column Despite Multiple Force Runs | Clay

8 comments

· Sorted by Oldest

Clay Support
APP
·
·
Status code 200 indicates successful HTTP responses, but errors can still occur in the processing step. Try these solutions:
Delete and recreate the column:
1.
Delete the affected Claygent column
2.
Create a fresh column with the same configuration
3.
This often resolves persistent processing issues
Force rerun the column:
Click the column header
Select "Force Rerun Column" to reset the stuck state
Alternative force run method:
Right-click the column
Hover over "Run Column" > "Force Run All Rows" [1]
If these steps don't resolve the issue and you need further help, request human assistance by clicking on "Talk to a person."
Clay Support
APP
·
·
Did that answer your question?
prateek
·
·
no
Clay Support
APP
·
·
I'm routing you to our human team now so they can assist you further with this issue.
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!
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
prateek
·
·
https://app.clay.com/workspaces/315182/tables/t_0t4ukfnGtUEKSACrjWa/views/gv_zW7TkbWgBfTe
Michael A.
·
·
Hi Prateek - thanks for reaching out!
The reason you're receiving this error is due to a rate limiting error from the HTTP API column. Means that you sent more requests to the API then is allowed within a given time period.
I've attached a screenshot from our HTTP API documentation here about rate limits:
To solve this you can either slow down your requests by trying 10-15 rows at a time OR in your HTTP API column you adjust the rate limits here depending on the specific API that you're working with (usually they have preferred rate limits described in their documentation!). Attached is a screenshot on where to find it:
Custom Rate Limits usually look like:
50 requests per minute: Request Limit: 50 | Duration: 60000 (60,000 milliseconds = 1 minute)
80 requests per minute: Request Limit: 80 | Duration: 60000
130 requests per minute: Request Limit: 130 | Duration: 60000
This is how I would approach this. Also sorry - a lot of information! Let me know if you need me to explain anything in more detail. Thanks!
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
·
·
Status code 200 indicates successful HTTP responses, but errors can still occur in the processing step. Try these solutions:
Delete and recreate the column:
1.
Delete the affected Claygent column
2.
Create a fresh column with the same configuration
3.
This often resolves persistent processing issues
Force rerun the column:
Click the column header
Select "Force Rerun Column" to reset the stuck state
Alternative force run method:
Right-click the column
Hover over "Run Column" > "Force Run All Rows" [1]
If these steps don't resolve the issue and you need further help, request human assistance by clicking on "Talk to a person."
Clay Support
APP
·
·
Did that answer your question?
prateek
·
·
no
Clay Support
APP
·
·
I'm routing you to our human team now so they can assist you further with this issue.
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!
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
prateek
·
·
https://app.clay.com/workspaces/315182/tables/t_0t4ukfnGtUEKSACrjWa/views/gv_zW7TkbWgBfTe
Michael A.
·
·
Hi Prateek - thanks for reaching out!
The reason you're receiving this error is due to a rate limiting error from the HTTP API column. Means that you sent more requests to the API then is allowed within a given time period.
I've attached a screenshot from our HTTP API documentation here about rate limits:
To solve this you can either slow down your requests by trying 10-15 rows at a time OR in your HTTP API column you adjust the rate limits here depending on the specific API that you're working with (usually they have preferred rate limits described in their documentation!). Attached is a screenshot on where to find it:
Custom Rate Limits usually look like:
50 requests per minute: Request Limit: 50 | Duration: 60000 (60,000 milliseconds = 1 minute)
80 requests per minute: Request Limit: 80 | Duration: 60000
130 requests per minute: Request Limit: 130 | Duration: 60000
This is how I would approach this. Also sorry - a lot of information! Let me know if you need me to explain anything in more detail. Thanks!
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!