Request Limit Bug Report: Immediate Attention Needed

Jordan C. · 2025-06-11 02:06:21.322982+00

Bug for request limit (please fix, it's an actual bug)

Request Limit Bug Report: Immediate Attention Needed | Clay

6 comments

· Sorted by newest

Anaum K.
·
·
Hey Jordan! From the video you sent, it seems like the main feedback you pointed out was to make it clearer in the UI that both fields (“Request Limit” and “Duration”) need to be filled out if you want to define a rate limit—I can confirm that’s exactly right! Regarding your point about the 120-second timeout and your Snowflake query timing out, our 120-second timeout for the HTTP API feature is currently a platform-wide limit, and we’re not able to increase this limit at the moment. Happy to help explore potential workarounds if you’d like!
Jordan C.
·
·
If they need to test it, they can duplicate this table on my account and adjust the snowflake query to basically say “try 100x harder and never stop, use 500,000 tokens…” and they likely can see it timeout. But my guess is you won’t need to do that.
Anaum K.
·
·
Thanks for following up! I’ll check in with the team to get an ETA and circle back with an update as soon as I have one.
🙏1
Jordan C.
·
·
Anaum K. can you provide an update on this? This feature is super key to me because cells timing out at 120 seconds kills my agentic workflows.
Anaum K.
·
·
Hello Jordan! Thanks for this! Really appreciate your feedback, so I'm glad you took a moment to share it with us. I'll relay this to our product owners. Let me know if you run into any other issues!
Channeled
APP
·
·
To fix the request limit issue, you can set a Request Limit and Duration in your HTTP API settings. The Request Limit specifies the maximum number of allowed requests, while the Duration sets the timeframe in milliseconds (between 1-900, 000 ms). For this to work properly, your rate limit must average at least 5 requests per second. Could you share more details about the specific error you're seeing? Please copy and paste any error messages or JSON responses you're receiving so I can help troubleshoot further.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University

Loading comments

Anaum K.
·
·
Hey Jordan! From the video you sent, it seems like the main feedback you pointed out was to make it clearer in the UI that both fields (“Request Limit” and “Duration”) need to be filled out if you want to define a rate limit—I can confirm that’s exactly right! Regarding your point about the 120-second timeout and your Snowflake query timing out, our 120-second timeout for the HTTP API feature is currently a platform-wide limit, and we’re not able to increase this limit at the moment. Happy to help explore potential workarounds if you’d like!
Jordan C.
·
·
If they need to test it, they can duplicate this table on my account and adjust the snowflake query to basically say “try 100x harder and never stop, use 500,000 tokens…” and they likely can see it timeout. But my guess is you won’t need to do that.
Anaum K.
·
·
Thanks for following up! I’ll check in with the team to get an ETA and circle back with an update as soon as I have one.
🙏1
Jordan C.
·
·
Anaum K. can you provide an update on this? This feature is super key to me because cells timing out at 120 seconds kills my agentic workflows.
Anaum K.
·
·
Hello Jordan! Thanks for this! Really appreciate your feedback, so I'm glad you took a moment to share it with us. I'll relay this to our product owners. Let me know if you run into any other issues!
Channeled
APP
·
·
To fix the request limit issue, you can set a Request Limit and Duration in your HTTP API settings. The Request Limit specifies the maximum number of allowed requests, while the Duration sets the timeframe in milliseconds (between 1-900, 000 ms). For this to work properly, your rate limit must average at least 5 requests per second. Could you share more details about the specific error you're seeing? Please copy and paste any error messages or JSON responses you're receiving so I can help troubleshoot further.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University