Rate limits - Clay implements rate limits for system stability, especially with heavier prompts or lower API tiers. If you're using OpenAI, you need tier 2 API access (30,000 TPM for content generation, 450,000 TPM for web research).
Missing required data - Check if your AI column has "Required to Run" fields enabled but the referenced cells are empty. [1]
API key issues - Verify your OpenAI API key is correct and has sufficient limits.
Column dependencies - If columns were changed multiple times or runs were stopped midway, they can get stuck in "Queued" status.
Quick fixes:
Try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)
Create a new column by duplicating the problematic one
Use conditional runs with Clay.getCellStatus() for dependent columns
Before we troubleshoot further, try using Sculptor (top-right corner) - it can help diagnose and fix AI column issues automatically. Let me know if that helps or if you need more specific troubleshooting!
Sorry about this. We've identified a system-wide bug affecting the Use AI columns. We’re already working on an urgent fix and it should be resolved shortly. You can monitor the status of the incident here: https://rootly.com/teams/clay/status-pages/clay-status/public
We can confirm that our engineers have pushed a fix here. Re-running the errored cells in the Use AI column/s in your table will resolve the issue on your end. Please let us know if you have any questions or concerns. Thank you again for your patience!
