Issue with Anthropic Claygent Feature: Retries and Timeouts

Everything ok with the Anthropic Claygent feature, im re-running a table I worked on a while ago, and now it's not working. Rows keep saying retrying and time out, and it does not seem to work (but it worked in the past) 🤦‍♂️ Even tried duplicating the column and running a more powerful model but nothing seems to work. 😒

6 comments

Channeled
APP
·
·
The issue you're experiencing with the Anthropic Claygent feature showing "Retrying" and timing out is likely due to API tier limits. This can happen especially if you're using a lower tier of Anthropic's API. To resolve this: 1. Try processing your data in smaller batches, around 50 rows at a time. 2. Check your Anthropic API settings and limits at https://console.anthropic.com/settings/limits. 3. Review the rate limits documentation at https://docs.anthropic.com/en/api/rate-limits for more details. If you're using a more powerful model, ensure you've set an appropriate Max Cost in the Claygent settings. For expensive models like GPT-4 Turbo or Claude, use at least $0.10 per request. If the issue persists after trying these steps, you may need further assistance. In that case, please request to talk to a person for more detailed support.
Source: Claygent (AI Web Researcher) with Artificial Intelligence
Jorge M.
·
·
Is there any way i can run only the rows that timed out? (in batches of 10 or 20 rows) Seems like the only way to work on my table is to manually run rows one by one (pretty shitty experience tbh)
Channeled
APP
·
·
Yes, there's a way to run only the rows that timed out without doing it manually one by one. You can use the "Run All Rows that haven't run or have errors" option. Here's how: 1. Right-click on the column you want to run 2. Click "Play" 3. Select "Run All Rows that haven't run or have errors" This will automatically process only the rows that encountered issues or didn't run previously, saving you time and effort. If you need more assistance with this or have any other questions, please don't hesitate to ask for further help.
Source: Run Options
Jorge M.
·
·
The issue with that option is that my table has 2k rows, and if I try that, it would run all the rest of the rows and kick-start the problem altogether.
Channeled
APP
·
·
Yes, there's a way to run only the rows that timed out without triggering the issue again. Here are a few options: 1. Run Starting from a Specific Row: Right-click the column, hover over "Run Column" > "Choose Number of rows to run", and specify the number of rows and starting row. 2. Use Conditional Runs: Set up a condition to only run rows that haven't been processed or have errors. This ensures you're not wasting credits on already processed rows. 3. Filter and Run: Filter for rows where the current column "is empty," then run the AI on those specific rows. By using these methods, you can process your data in smaller batches, avoiding the timeout issues while still completing your 2,000-row table.
Sources: AI Formulas + Conditional Runs [Clay 101] - Clay University Run Options
Channeled
APP
·
·