To address Claygent running slowly or getting stuck at 48% with many "0 Records Found" errors:
Try breaking your data into smaller batches (e.g., 50 rows at a time), especially if you’re on a lower API tier, as large runs can hit rate limits and slow processing .
For stuck or queued columns, right-click the column header and select Force Rerun Column to reset and jump-start the process .
If the column remains stuck, duplicate it, filter for rows where the column is empty, and run the new column on those rows. You can then merge the results back in .
Check your input data and search parameters for accuracy, as "0 Records Found" often means missing or mismatched inputs .
For large tables, performance may lag—try a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) to clear any UI issues .
When testing new workflows, start with a small sample (about 10 rows) to catch errors early before scaling up [1].
If you need further help, you can request human assistance by clicking on "Talk to a person."
If you still need help resolving the issue with Claygent running slowly or stuck, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
Just got word back from our Support Engineer and looks like you probably reached the rate limits on your OpenAI API key. Some ways around this is to increase your rate limit through OpenAI (upgrade your plan) or use our own Clay API key which will return results.
