Troubleshooting Long-Running AI Agent Tables

Drishti J. · 2025-11-15T10:57:20.161Z

My Ai agent is not working, all tables are running for more than 20 mins and no results.

Troubleshooting Long-Running AI Agent Tables | Clay

Clay Support
APP
·
·
The "Some inputs missing" message indicates your AI agent can't run because required fields are empty. [1]
To fix this:
1.
Check for missing inputs - Click into the cells showing "Some inputs missing" to see which specific fields are empty
2.
Verify required fields - Ensure all columns that your AI agent references contain data before it runs
3.
Try re-running - Click "re-run this cell" on affected rows, or toggle auto-update off and on again
4.
Hard refresh - If cells remain stuck: • Windows: Ctrl + Shift + R • Mac: Cmd + Shift + R
Once you populate the missing input fields, your AI agent should process normally.
Clay Support
APP
·
·
Did that help you fix the issue?
Drishti J.
·
·
I tried re-running, re starting and logging in again into clay as well. The column worked for first 5k rows and then for the last stretch it started acting up
Clay Support
APP
·
·
Since your AI column worked for the first 5k rows but stopped processing after that, this is likely a "Queued" issue that happens when columns are changed or runs are stopped midway.
Here's how to fix it:
1.
Create a duplicate column - Copy your current AI column
2.
Filter for empty rows - Filter where the original column "is empty"
3.
Run the new column on just those filtered rows
4.
Merge the results - Use the "merge columns" feature to combine both columns
You can also click into the specific cells showing issues to see more details about any error messages.
If this doesn't resolve it, monitor your usage limits and API quotas, as rate limits can affect processing for larger batches.
Clay Support
APP
·
·
Did that help resolve your processing issue?
Drishti J.
·
·
I decided to do that but the new column is also not running
Clay Support
APP
·
·
Try using Force Rerun Column to jumpstart the stuck column:
1.
Click the column header
2.
Hover over "Run column"
3.
Select Force to force the run
If that doesn't work, try a hard refresh:
Windows: Ctrl + Shift + R
Mac: Cmd + Shift + R
Also verify that auto-update is enabled for your table—if it's disabled at the table level, it overrides column settings and prevents columns from running. [1]
Click into the specific cells to see detailed error messages that might reveal what's blocking the runs.
Clay Support
APP
·
·
Did that fix the stuck column issue?
Clay Support
APP
·
·
If you still need help with your AI agent not running properly, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or any specific errors you’re encountering?
Drishti J.
·
·
No issue still persists. Claygent is not working in other sheets as well
Clay Support
APP
·
·
I'm sorry to hear the issue is still persisting. I'll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Drishti J.
·
·
https://app.clay.com/workspaces/237669/workbooks/wb_0t5ppnd4cE4yAUvRvqx/tables/t_0t5px9tpVQZeDucUE3s/views/gv_0t5px9tU59pPAa2RU6V
Bo (.
·
·
Hey,
This is expected with your setup. You’re running multiple tables at the same time using your own API key, and that key is hitting its rate limits. Once that happens, every table slows down or stalls because they’re all competing for the same limited capacity.
The best move is to avoid running several AI agents at once. Try running just one table at a time and things should move normally again.
Let me know if you have more questions.
Drishti J.
·
·
Hello, Thank you for your response, however I was just running one column when it was not giving any results I thought I should check if it's the issue with the column so I duplicated the column and ran the first row to crosscheck that's all.

17 comments