Troubleshooting AI Actions Stuck After Table Duplication

Gustavo S. · 2026-01-19T20:44:18.448Z

Hi team, I need help to debug what's happening. I duplicated a table and tried to run my AI actions and it gets stuck all the time. It seems this doesn't gets through. What might be the reasons?

Troubleshooting AI Actions Stuck After Table Duplication | Clay

9 comments

· Sorted by Oldest

Clay Support
APP
·
·
When AI columns get stuck like this after duplicating a table, it's usually because the column got into a queued state during the duplication process.
Try this fix: Click on your "AI - find domain" column header, then select "Force Rerun Column" from the dropdown. This should reset the stuck state and get things moving again.
If that doesn't work, you can also try clicking into one of the stuck cells and select "re-run this cell", or toggle auto-update off and back on for the whole table.
The "Tuning/Refining/Formulating" status you're seeing is normal for AI columns, but it shouldn't stay stuck at 0% - the force rerun should resolve that.
Clay Support
APP
·
·
Is that what you were looking for?
Gustavo S.
·
·
tried your solutions but they didn't work
Clay Support
APP
·
·
I'm sorry to hear that the solutions didn't work. I'll connect you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
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)
Gustavo S.
·
·
here's my table: https://app.clay.com/workspaces/788481/workbooks/wb_0t8yrnpsNtqD625upHW/tables/t_0t94pbmKgz4ofXmppM9/views/gv_0t93x20STiDBQZYXaZ3
Gustavo S.
·
·
I think I found the issue. It seems I was using a Google AI model "Flash" with issues. Don't know why. Whenever I changed for the model Helium from Clay it started working.
Daniela D.
·
·
Hey Gustavo! Thanks for reaching out. Happy to help✨. The team confirmed that the rate limit issues with Google Gemini are due to capacity limits on Google’s side. We’re rolling out improvements to help reduce errors when using Clay Credits, and we’ll share updates as things improve. In the meantime, we recommend using a different model to run this. Let us know if you still run into any issues.
1
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
·
·
When AI columns get stuck like this after duplicating a table, it's usually because the column got into a queued state during the duplication process.
Try this fix: Click on your "AI - find domain" column header, then select "Force Rerun Column" from the dropdown. This should reset the stuck state and get things moving again.
If that doesn't work, you can also try clicking into one of the stuck cells and select "re-run this cell", or toggle auto-update off and back on for the whole table.
The "Tuning/Refining/Formulating" status you're seeing is normal for AI columns, but it shouldn't stay stuck at 0% - the force rerun should resolve that.
Clay Support
APP
·
·
Is that what you were looking for?
Gustavo S.
·
·
tried your solutions but they didn't work
Clay Support
APP
·
·
I'm sorry to hear that the solutions didn't work. I'll connect you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
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)
Gustavo S.
·
·
here's my table: https://app.clay.com/workspaces/788481/workbooks/wb_0t8yrnpsNtqD625upHW/tables/t_0t94pbmKgz4ofXmppM9/views/gv_0t93x20STiDBQZYXaZ3
Gustavo S.
·
·
I think I found the issue. It seems I was using a Google AI model "Flash" with issues. Don't know why. Whenever I changed for the model Helium from Clay it started working.
Daniela D.
·
·
Hey Gustavo! Thanks for reaching out. Happy to help✨. The team confirmed that the rate limit issues with Google Gemini are due to capacity limits on Google’s side. We’re rolling out improvements to help reduce errors when using Clay Credits, and we’ll share updates as things improve. In the meantime, we recommend using a different model to run this. Let us know if you still run into any issues.
1
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!