Performance issues in Clay are typically caused by large tables, multiple simultaneous actions, or API rate limits.
Try a hard refresh first:
Mac: Command + Shift + R (Chrome/Firefox) or Option + Command + E (Safari)
Windows: Ctrl + F5 or Ctrl + Shift + R
If using AI enrichments, slow performance often indicates API tier limits. Process data in smaller batches of around 50 rows at a time. For Claygent specifically, ensure your search queries are specific and break large requests into smaller batches.
Rate limits are enforced per row/column, and newer columns may face more frequent limits due to conservative token usage estimates.
If you still need help with the slow performance issue, I’m here to assist you further. Would you like to provide more details about what you’re trying to resolve or understand?
