For slow Claygent processing, try these solutions:
Immediate fixes:
** Hard refresh your browser: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
** Break large requests into smaller batches
Common causes:
** API tier limits requiring smaller batch processing (around 50 rows at a time)
** Large tables with multiple simultaneous actions causing latency
** Network connection issues
*For stuck "queued" tasks:
Create a new column by duplicating the current one and run it on remaining rows
Make sure your search queries are specific and check your usage limits and API quotas
For a column stuck running for 3+ hours on 700 rows, try these solutions:
Delete and recreate the column:
1. Delete the affected column
2. Create a fresh column with the same prompt
3. Re-run it
Force run option:
** Use Force Run in the table settings (may take time depending on table size)
Break into smaller batches:
** Process around 50 rows at a time instead of all 700
Performance factors:
Large tables with multiple simultaneous actions can cause latency issues
The delete/recreate approach is often most effective for stuck columns.
Hi Richard - thanks so much for reaching out and sorry to hear that you're having issues here. Do you mind sending me the table you're currently working in so I can take a closer look here?
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in Clay Support.
