Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hello, 

One of my Zaps has stopped working after a few successful submissions just before the error. It’s connected to Facebook on one end and Dynamics 365 on the other; the error message goes like ‘The app returned - There is an unterminated literal at position 126’.

Please advise of possible solutions. 

Thank you!

Hi @Arbor Memorial 

Good question.

 

Have you reviewed the help articles for each app in the Zap?

https://zapier.com/apps/microsoft-dynamics-crm/help

 

Which Facebook app are you using in the Zap?

 

You may want to open a ticket with Zapier Support for further help: https://zapier.com/app/get-help

 

Hey @Arbor Memorial! Hmm, I haven’t seen this error before and without looking at your Zap steps and where this error is appearing, it’s a bit tough to diagnose. I see that you submitted a support ticket; our support team is going to be best suited to look into this one for you.

We’ll be following along that thread but please feel free to circle back to this post if you have any solutions/developments to share in the meantime!

@Troy Tessalone , @jesse 

Thank you very much for replying and for suggestions. The error seems to have resolved (or maybe paused) with a few system refreshes but no idea what could’ve triggered it. I will update the thread if I have any solid inputs around such an error. thanks again!

Take care!

Hey @Arbor Memorial so glad to hear you were able to get this working after a few system refreshes! In the meantime, I wanted to share that the error you’re running into looks like a bug. I see you’ve been added to the issue already, so you’ll be notified once we have a full resolution. We’ll also circle back to this thread to post any updates in the meantime for anyone else that may be experiencing the same issue. 

Terms & Conditions