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.

Question

Can we provide more error details to the user?

  • November 17, 2022
  • 1 reply
  • 38 views
Left Hook

Aloha all!

 

First time we’ve run into the question: the user-facing error message is getting truncated when sending back a long string (In cases where there’s a lot of data for the user to take action on).

Is there a way to return an object to the Zapier editor so that the user can drill down further instead of getting a truncated message?

Or are we just limited to a character limit for the string and that’s that?

If so, what’s the character limit?

 

Thanks for the help!

 

Best,

~Sean and team

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

    1 reply

    iansco
    Forum|alt.badge.img+1
    • ianscoZapier Staff
    • Zapier Staff
    • November 21, 2022

    Hey Sean / Team @Left Hook! 👋

    ...the user-facing error message is getting truncated when sending back a long string…

    Is there a way to return an object to the Zapier editor so that the user can drill down further instead of getting a truncated message?

    When it comes to showing errors in the Zap Editor, there isn’t currently a way to return an “object” that would present users with a UI that would offer a way to navigate/drill-down into that “object”. 

    Or are we just limited to a character limit for the string and that’s that?

    If so, what’s the character limit?

    I created an action that returns an error message (via z.error.Errors) that has 1,000 words in the error message. The first 247 characters are initially displayed but a “Show More” link displays all 1,000 words after it is clicked on. This provides the ability to display a lot more information in the Zap Editor than would probably be considered user-friendly for an error message:

    d943bcbfb564e8d4e3acad9c5c03f312.pngThe Zap History page takes the same approach. However, due to UI constraints, it shows much less of the error message when the “Show Details” link is clicked on:

    ed34a105d538478233326891499d2bf2.png

    In cases where there’s a lot of data for the user to take action on

    Please could you post some more details (screenshot / mockups etc) that show an example of this kind of error and how and where you’d like users to be able to view that information? 

    That will help us to make further suggestions on what’s currently possible but also to create a new feature request for any changes you’d like to see 👍

    Terms & ConditionsAccessibility statement