Skip to main content
Question

Failed to create a row in Snowflake

  • September 10, 2025
  • 2 replies
  • 40 views

Curious to see if anyone has experienced our issue.  We are connecting a feathery form to a table in a Snowflake data warehouse via Zapier.  We have configured both Feathery and our connection to Snowflake properly. The issue is in our mappings  Visually we see that we have mapped properly.  However, when we test run we get the following error message:

Failed to create a row in Snowflake

Failed: {"message":"Failed: DML operation to table xxxxxx.xxxxx.FEATHERYFORMSUBMIT failed on column LASTMODIFIEDDATETIME with error: Timestamp 'xxxxxxx@gmail.com' is not recognized"}

Zapier is shifting or swapping a field to incorrectly write to another field.  At first it seemed it was shifting data from one field to write to the field that immediately followed.  However, we have seen the gap greater than that; they are not adjacent to each other.  

It’s only a two step zap, a feathery form completion and the zap to write to the snowflake table.  

We processed a test run and selected a test record in the first step. We mapped the selected fields we needed and visually confirmed that they are in fact properly mapped, name to name, email to email, etc., five fields in all.  Each time we run it we get the same error and visually can’t see anything we did that would trip it.  

Thanks.

 

 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

Sparsh from Automation Jinn
Forum|alt.badge.img+6

Hey ​@TSAEsZap,

Please share the Data In and Data Out screenshots as well as how the apps are configured for us to have more context.

Looking at just the error message, it seems to be mapping issue where you are trying to give an email format in the timestamp field.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9723 replies
  • September 16, 2025

Hi there ​@TSAEsZap 👋

That’s really strange. Can you try refreshing the fields on the Snowflake action to make sure the Zap is looking at the most up to date set of fields? Just wondering if a new field was created or there was a change on Snowflake’s end that caused the ordering or mapping of the fields to be out of sync somehow. 🤔

Keep us posted on how it goes, want to make sure this gets sorted!