Issues with AI Processing in Claygent: Request Stuck for Hours

John V. · 2025-12-05T13:55:31.980Z

Is anyone else having trouble using AI with Claygent? It's stuck processing the request for hours. Have tried deleting the column and retrying but still gives me the same problem

Issues with AI Processing in Claygent: Request Stuck for Hours | Clay

15 comments

· Sorted by Oldest

Clay Support
APP
·
·
That cycling through processing statuses definitely looks like you're hitting an infinite loop. This typically happens when an enrichment column triggers based on a field that it updates itself, causing continuous re-runs. [1]
Try these immediate fixes:
Pause auto-run on the Claygent column [2]
Hard refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)
Create a new column by duplicating the current one and run it on rows where the original is empty
The "queued" issue often happens when columns are changed multiple times or runs are stopped midway.
What specific data is your Claygent column trying to process, and does it reference any other columns in your table?
John V.
·
·
Connect to a human please
Clay Support
APP
·
·
I understand your frustration, and I’m connecting 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)
Andrew Q.
·
·
Hey John! Is it this table here you're referring to? If so, your prompt seems to be rather long. I recommend keeping at max 2-4 requests for Claygent prompts and opening more up to allow it to process better.
John V.
·
·
Hey Andrew. I made the prompt shorter, but it's still not processing the request.
Andrew Q.
·
·
Hey John! Should've clarified that this tip was moving forward. Since it was still running, I'm not sure confident that it would speed up the process. Could you reach back out if it doesn't return an output by the end of the day? I will also try to see if this is a larger issue and return to update you if it is, but it shouldn't be.
Aubry S.
·
·
John V. What model are you using? I had this issue yesterday. Seems to be resolved today (using GPT-5-Mini).
John V.
·
·
Aubry S. 4.1 mini
Aubry S.
·
·
Using Clay's key or your own? If your own, what usage tier are you?
Michael A.
·
·
Hi - happy to help! It might be due to your output format trying to have 9 evaluation functions for a mini model. I'd potentially configure that into multiple steps first.
John V.
·
·
I changed it to only have 1 and it's still giving me the same issue Michael A.
John V.
·
·
Any way I can get some on one one help with this? Been over a day this has been going on
Bo (.
·
·
Hey, I checked your table and the issue is coming from your own API key. It’s hitting its rate limits, which is why the Claygent step keeps getting stuck. There isn’t a workaround on our side for that. If you switch the step to use Clay’s API key instead, it should run normally.
I also saw you tested with Gemini. Gemini has very low rate limits by default, so it’ll run into the same problem with larger batches.
If you want to keep using your own key, you’d need to increase your tier with the provider. Otherwise, using Clay credits will give you the higher limits you need for this workflow.
Let me know if you have more questions
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
That cycling through processing statuses definitely looks like you're hitting an infinite loop. This typically happens when an enrichment column triggers based on a field that it updates itself, causing continuous re-runs. [1]
Try these immediate fixes:
Pause auto-run on the Claygent column [2]
Hard refresh your browser (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)
Create a new column by duplicating the current one and run it on rows where the original is empty
The "queued" issue often happens when columns are changed multiple times or runs are stopped midway.
What specific data is your Claygent column trying to process, and does it reference any other columns in your table?
John V.
·
·
Connect to a human please
Clay Support
APP
·
·
I understand your frustration, and I’m connecting 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)
Andrew Q.
·
·
Hey John! Is it this table here you're referring to? If so, your prompt seems to be rather long. I recommend keeping at max 2-4 requests for Claygent prompts and opening more up to allow it to process better.
John V.
·
·
Hey Andrew. I made the prompt shorter, but it's still not processing the request.
Andrew Q.
·
·
Hey John! Should've clarified that this tip was moving forward. Since it was still running, I'm not sure confident that it would speed up the process. Could you reach back out if it doesn't return an output by the end of the day? I will also try to see if this is a larger issue and return to update you if it is, but it shouldn't be.
Aubry S.
·
·
John V. What model are you using? I had this issue yesterday. Seems to be resolved today (using GPT-5-Mini).
John V.
·
·
Aubry S. 4.1 mini
Aubry S.
·
·
Using Clay's key or your own? If your own, what usage tier are you?
Michael A.
·
·
Hi - happy to help! It might be due to your output format trying to have 9 evaluation functions for a mini model. I'd potentially configure that into multiple steps first.
John V.
·
·
I changed it to only have 1 and it's still giving me the same issue Michael A.
John V.
·
·
Any way I can get some on one one help with this? Been over a day this has been going on
Bo (.
·
·
Hey, I checked your table and the issue is coming from your own API key. It’s hitting its rate limits, which is why the Claygent step keeps getting stuck. There isn’t a workaround on our side for that. If you switch the step to use Clay’s API key instead, it should run normally.
I also saw you tested with Gemini. Gemini has very low rate limits by default, so it’ll run into the same problem with larger batches.
If you want to keep using your own key, you’d need to increase your tier with the provider. Otherwise, using Clay credits will give you the higher limits you need for this workflow.
Let me know if you have more questions
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!