Can't seem to import a CSV. Repeatedly running into this

·

· Sorted by Oldest

Clay
APP
·
·
Here are the most common CSV import fixes: File Requirements: ** Remove "created at" or "updated at" columns ** Maximum 72 columns and 50,000 rows ** Use UTF-8 encoded CSV with comma separators ** Keep file name short Quick Fix: Upload your data to Google Sheets, download as CSV, then try importing again Field Issues: Remove commas, colons, and semicolons from your CSV data if fields are getting mixed up If you need further help, request human assistance by clicking "Talk to a person."
Bo (Clay)
·
·
parthi - 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!
Clay
APP
·
·
Hi there! Thank you for your patience -- I'm confirming that our engineers have fixed this issue and all tables should be working as expected. Please let us know if you're still running into any issues!

Clay
APP
·
·
Here are the most common CSV import fixes: File Requirements: ** Remove "created at" or "updated at" columns ** Maximum 72 columns and 50,000 rows ** Use UTF-8 encoded CSV with comma separators ** Keep file name short Quick Fix: Upload your data to Google Sheets, download as CSV, then try importing again Field Issues: Remove commas, colons, and semicolons from your CSV data if fields are getting mixed up If you need further help, request human assistance by clicking "Talk to a person."
Bo (Clay)
·
·
parthi - 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!
Clay
APP
·
·
Hi there! Thank you for your patience -- I'm confirming that our engineers have fixed this issue and all tables should be working as expected. Please let us know if you're still running into any issues!