hey guys I'm receiving an error when trying to export data from clay table as csv. here's the error in short loom: https://www.loom.com/share/445ad1fd5e4c48248ee4bc7d19a13173
Try logging out of Clay and logging back in to refresh your session token - this often resolves export errors.
If that doesn't work, the issue might be with AI-enhanced columns that don't export properly. Create a dedicated export view by duplicating your current table view and removing any unnecessary columns, keeping only the essential data you need. [1]
This ensures a clean export without problematic object fields that can cause errors.
Was that helpful?
Since the logout/login didn't work, let's try creating a clean export view. The issue is likely with problematic columns that don't export well. [1]
Duplicate your current view, then hide any AI-enhanced columns, object fields, or integration columns showing "run condition not met" - these often cause export errors. Keep only the essential raw data columns you need. [2]
Once you've cleaned up the view, try exporting again from Actions > Export > Download CSV.
Did that answer your question?
hasn't been resolved. please connect me to a human agent
Got it — I’m connecting you to a human teammate now.
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!

hey guys?
Petar - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog.
For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change.
So what happens now?
Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you.
Do you have any further questions before I step away from this conversation until I have an update for you?
