Why is Clay Delaying AI Response Times Compared to Expected Output?

·

Column with an AI researcher takes over 2 minutes in a queue, where on output it says that it took only 15 or 20 seconds for IA to get a response. My question is, in that case, why is Clay delaying the output? I use my OpenAI key so it seems clay column is making that queue 10 times longer...

1 comment

· Sorted by Oldest

Channeled
APP
·
·
The discrepancy between queue time and reported processing time can occur due to several factors. Loading delays are common with larger tables, which can take longer to update. Performance issues may also arise when multiple actions are running simultaneously, causing latency where cell data takes longer to load. For Claygent specifically, you need an OpenAI API key with Tier 2 or higher (≥450, 000 TPM) for optimal performance. If your API key has lower limits, this could cause processing delays despite using your own key. Try performing a hard refresh (Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac) to see if that resolves the issue.
Source: AI Tokens | Documentation | Clay University

Channeled
APP
·
·
The discrepancy between queue time and reported processing time can occur due to several factors. Loading delays are common with larger tables, which can take longer to update. Performance issues may also arise when multiple actions are running simultaneously, causing latency where cell data takes longer to load. For Claygent specifically, you need an OpenAI API key with Tier 2 or higher (≥450, 000 TPM) for optimal performance. If your API key has lower limits, this could cause processing delays despite using your own key. Try performing a hard refresh (Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac) to see if that resolves the issue.
Source: AI Tokens | Documentation | Clay University