Issues with Clay Functions: Unable to Create or Edit

Jacob T. · 2025-12-16T19:24:02.981Z

I'm unable to use Clay functions at all. They're available in my workspace and I was able to create/use several. however, now I'm unable to create new ones, edit their name, update their settings, etc. It seems like I may have hit an account limit? I only have a few though. Please advise! This is disrupting some customer operations. https://www.loom.com/share/2e897fe2391145879bbff5b52dfd2fbb https://app.clay.com/workspaces/129266/functions

Issues with Clay Functions: Unable to Create or Edit | Clay

9 comments

· Sorted by Oldest

Clay Support
APP
·
·
That's frustrating—let me help identify what's happening. This could be related to workspace limits or permissions.
Possible causes:
Credit spend limits: If your workspace has credit limits set, hitting them stops all credit-consuming processes [1]
Row limits: Workspaces have total row limits that can prevent new operations
Role permissions: Only Admins can manage certain workspace settings and resources [2]
Quick troubleshooting:
1.
Check if you're seeing any limit-reached messages in your workspace
2.
Verify your role permissions with your workspace Admin
3.
Try using Sculptor (top-right corner) to build functions—it's free and might bypass the issue
Can you try Sculptor first and let me know if that helps? If not, I can connect you with a human teammate to investigate your specific workspace limits.
Jacob T.
·
·
human?
Clay Support
APP
·
·
I understand this is disrupting your operations. Would you like me to connect you with a human agent? Or if you want, you can try using Sculptor or provide more details so I can assist further.
Jacob T.
·
·
human
Clay Support
APP
·
·
I’m routing you to our human team now. They’ll be able to 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)
LuisArturo
·
·
Hey there Jacob thanks for reaching out, this is occurring due to a bug on our hands. Our engineering team is looking into this issue at the moment. We'll follow up here as soon as we know more!
Jacob T.
·
·
Thank you!
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed.
Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble.
Thank you for your patience as we worked on it.

Clay Support
APP
·
·
That's frustrating—let me help identify what's happening. This could be related to workspace limits or permissions.
Possible causes:
Credit spend limits: If your workspace has credit limits set, hitting them stops all credit-consuming processes [1]
Row limits: Workspaces have total row limits that can prevent new operations
Role permissions: Only Admins can manage certain workspace settings and resources [2]
Quick troubleshooting:
1.
Check if you're seeing any limit-reached messages in your workspace
2.
Verify your role permissions with your workspace Admin
3.
Try using Sculptor (top-right corner) to build functions—it's free and might bypass the issue
Can you try Sculptor first and let me know if that helps? If not, I can connect you with a human teammate to investigate your specific workspace limits.
Jacob T.
·
·
human?
Clay Support
APP
·
·
I understand this is disrupting your operations. Would you like me to connect you with a human agent? Or if you want, you can try using Sculptor or provide more details so I can assist further.
Jacob T.
·
·
human
Clay Support
APP
·
·
I’m routing you to our human team now. They’ll be able to 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)
LuisArturo
·
·
Hey there Jacob thanks for reaching out, this is occurring due to a bug on our hands. Our engineering team is looking into this issue at the moment. We'll follow up here as soon as we know more!
Jacob T.
·
·
Thank you!
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed.
Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble.
Thank you for your patience as we worked on it.