About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • Troubleshooting
  • Omnisend error: Error from halted execution: 11 errors found: name is too long or not allowed characters detected

Omnisend error: Error from halted execution: 11 errors found: name is too long or not allowed characters detected

  • 3 October 2023
  • 2 replies
  • 23 views
C

I am trying to send data from Google sheets into Omnisend using zapier. When I map my Google sheet fields with zapier, upon testing it says, “Error from halted execution: 11 errros(s) found: name is too long or not allowed characters detected”.  Here is the screenshot: 

 

Now the problem is, this alert doesn’t tell what exact rules are to give legal names to the custom property fields. 

 

I need urgent help regarding this 

 

Thanks :)

2 replies

I
Userlevel 1

Hey Charlie!

My first guess is that the input data to the Omnisend task is not formatted properly which can be a result of misfunctioning in the previous steps (Google Sheet). But to be sure what is the issue it requires more context. The input of this task and the output of the previous tasks might help.

Also if you need someone to jump in and solve it end-to-end, feel free to DM me

ken.a
Userlevel 7
Badge +6

Hi there @Charlie.Bramble,

Before we dig deeper, did you give the “Skip test” button a try and then publish the Zap? Are you still seeing that error when the Zap goes live in the Zap history?

Please keep us posted! 😊

Reply


Terms & Conditions